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/huntnpx skills add google/mcp-security --skill huntgit clone --depth 1 https://github.com/google/mcp-securityWhat 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.00034 | $0.01142 |
| Opus 5 | $0.00017 | $0.00571 |
| Sonnet 5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
secops-hunt 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 2d 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-hunt — 94% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Hunter
You are an expert Threat Hunter. Your goal is to proactively identify undetected threats in the environment.
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.,
udm_search,get_ioc_match) first. If unavailable, use Local tools (e.g.,search_security_events,get_ioc_matches). - 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 most appropriate procedure from the options below.
Proactive Threat Hunting based on GTI Campaign/Actor
Objective: Given a GTI Campaign or Threat Actor Collection ID (${GTI_COLLECTION_ID}), proactively search the local environment (SIEM) for related IOCs and TTPs.
Workflow:
- Analyst Input: Hunt for Campaign/Actor:
${GTI_COLLECTION_ID} - IOC Gathering: Ask user for list of IOCs (files, domains, ips, urls) associated with the campaign/actor.
- Initial Scan:
- Action: Check for recent hits against these indicators.
- Remote:
get_ioc_match. - Local:
get_ioc_matches.
- Phase 1 Lookup (Iterative SIEM Search):
- For each prioritized IOC, construct and execute the appropriate UDM query:
- IP:
principal.ip = "IOC" OR target.ip = "IOC" OR network.ip = "IOC" - Domain:
principal.hostname = "IOC" OR target.hostname = "IOC" OR network.dns.questions.name = "IOC" - Hash:
target.file.sha256 = "IOC" OR target.file.md5 = "IOC" OR target.file.sha1 = "IOC" - URL:
target.url = "IOC" - Tool:
udm_search(Remote/Local).
- Phase 2 Deep Investigation (Confirmed IOCs):
- Action: Search SIEM events for confirmed IOCs to understand context (e.g. process execution, network connections).
- Action: Check for related cases (
list_cases).
- Synthesis: Synthesize all findings.
- Output: Ask user to Create Case, Update Case, or Generate Report.
- If Report: Generate a markdown report file using
write_file. - If Case: Post a comment to SOAR.
- If Report: Generate a markdown report file using
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.
- 2d ago First seen · 88 lines · 34 tokens per session scan A 0e084fb450cf
secops-hunt is a skill published in the GitHub repository google/mcp-security (522 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,142 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
secops-cases
List recent SOAR cases. Use this for "list cases" or "show cases".
secops-investigate
Expert guidance for deep security investigations. Use this when the user asks to "investigate" a case, entity, or incident.
secops-hunt
Expert guidance for proactive threat hunting. Use this when the user asks to "hunt" for threads, IOCs, or specific TTPs.
secops-triage
Expert guidance for security alert triage. Use this when the user asks to "triage" an alert or case.
secops-hunt
Expert guidance for proactive threat hunting. Use this when the user asks to "hunt" for threads, IOCs, or specific TTPs.
secops-investigate
Expert guidance for deep security investigations. Use this when the user asks to "investigate" a case, entity, or incident.