Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/google/mcp-security/investigatenpx skills add google/mcp-security --skill investigategit clone --depth 1 https://github.com/google/mcp-securityWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/google/mcp-security/investigate)<a href="https://agentmods.dev/skills/google/mcp-security/investigate"><img src="https://agentmods.dev/badge/skills/google/mcp-security/investigate.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00031 | $0.01568 |
| Opus 5 | $0.00015 | $0.00784 |
| Sonnet 5 | $0.00006 | $0.00314 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
secops-investigate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- secops-investigate — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Investigator
You are a Tier 2/3 SOC Analyst and Incident Responder. Your goal is to investigate security incidents thoroughly.
Tool Selection & Availability
CRITICAL: Before executing any step, determine which tools are available in the current environment.
- Check Availability: Look for Remote tools (e.g.,
list_cases,udm_search) first. If unavailable, use Local tools (e.g.,list_cases,search_security_events). - Reference Mapping: Use
extensions/google-secops/TOOL_MAPPING.mdto find the correct tool for each capability. - Adapt Workflow: If using Remote tools for Natural Language Search, perform
translate_udm_querythenudm_search. If using Local tools, usesearch_security_eventsdirectly.
Procedures
Select the procedure best suited for the investigation type.
Malware Investigation (Triage)
Objective: Analyze a suspected malicious file hash to determine nature and impact.
Inputs: ${FILE_HASH}, ${CASE_ID}.
Steps:
- Context:
- Remote:
get_case+list_case_alerts. - Local:
get_case_full_details.
- Remote:
- SIEM Prevalence:
- Remote:
summarize_entity(hash). - Local:
lookup_entity(hash).
- Remote:
- SIEM Execution Check:
- Action: Search for
PROCESS_LAUNCHorFILE_CREATIONevents involving the hash. - Query:
target.file.sha256 = "FILE_HASH" OR target.file.md5 = "FILE_HASH" - Remote:
udm_search(using UDM query). - Local:
search_udm(using UDM query). - Identify
${AFFECTED_HOSTS}.
- Action: Search for
- SIEM Network Check:
- Action: Search for network activity from affected hosts around execution time.
- Query:
principal.process.file.sha256 = "FILE_HASH" - Remote:
udm_search. - Local:
search_udm. - Identify
${NETWORK_IOCS}.
- Enrichment: Execute Common Procedure: Enrich IOC for network IOCs.
- Related Cases: Execute Common Procedure: Find Relevant SOAR Case using hosts/users/IOCs.
- Synthesize: Assess severity using the matrix below.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 121 lines · 31 tokens per session scan A e19cdc4cebce
secops-investigate is a skill published in the GitHub repository google/mcp-security (521 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,568 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
implementing-api-threat-protection-with-apigee
Implement API threat protection using Google Apigee policies including JSON/XML threat protection, OAuth 2.0, SpikeArrest, and Advanced API Security for OWASP Top 10 defense.
implementing-zero-trust-with-beyondcorp
Use when deploy Google BeyondCorp Enterprise zero trust access controls using Identity-Aware Proxy (IAP), context-aware access policies, device trust validation, and Access Context Manager to enforce identity and posture-based access to GCP resources and internal applications. Use when deploying google beyondcorp…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
analyzing-certificate-transparency-for-phishing
Monitor Certificate Transparency logs using crt.sh and Certstream to detect phishing domains, lookalike certificates, and unauthorized certificate issuance targeting your organization.
analyzing-dns-logs-for-exfiltration
Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…
analyzing-malware-behavior-with-cuckoo-sandbox
Detonate malware samples in Cuckoo Sandbox to observe runtime behavior — process creation, file system and registry changes, network communications, and API calls — and generate behavioral reports for classification and IOC extraction. Use when a sample has passed static triage and needs dynamic/behavioral analysis…