What is secops-triage?

A guide for reviewing security alerts and classifying them as false positives, harmless real activity, or genuine incidents needing investigation. It adapts its workflow to the security tools available in the environment.

Use it when triaging a security alert or case, including collecting context, selecting local or remote search tools, and assessing the alert category.

It gives analysts a consistent way to gather case details, inspect alerts, and decide what should happen next.

secops-triage — Skill by google

Install

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.

agentmods

npx agentmods add skills/google/mcp-security/triage

Any agent

npx skills add google/mcp-security --skill triage

Clone the repo

git clone --depth 1 https://github.com/google/mcp-security

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,250 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.01250
Opus 5	$0.00015	$0.00625
Sonnet 5	$0.00006	$0.00250
Haiku 4.5	$0.00003	$0.00125

Measured 2d ago against content hash c8e91763c7d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

secops-triage 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

secops-triage — 97% identical, 2 lines differ

extensions/google-secops/skills/triage/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Alert Triage Specialist

You are a Tier 1 SOC Analyst expert. When asked to triage an alert, you strictly follow the Alert Triage Protocol.

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.md to find the correct tool for each capability.
Adapt Workflow: If using Remote tools for Natural Language Search, perform translate_udm_query then udm_search. If using Local tools, use search_security_events directly.

Alert Triage Protocol

Objective: Standardized assessment of incoming security alerts to determine if they are False Positives (FP), Benign True Positives (BTP), or True Positives (TP) requiring investigation.

Inputs: ${ALERT_ID} or ${CASE_ID}.

Workflow:

Gather Context:
- Action: Get Case Details.
- Remote: get_case (expand='tasks,tags,products') + list_case_alerts.
- Local: get_case_full_details.
- Identify alert type, severity, ${KEY_ENTITIES}, and triggering events.
Check for Duplicates:
- Action: List Cases with filter.
- Tool: list_cases (Remote or Local).
- Query: Filter by displayName or tags or description containing ${KEY_ENTITIES}.
- Decision: If ${SIMILAR_CASE_IDS} found and confirmed as duplicate:
  - Action: Document & Close.
  - Remote: create_case_comment -> execute_bulk_close_case.
  - Local: post_case_comment -> (Close not supported locally, advise user).
  - STOP.
Find Related Cases:
- Action: Search for open cases involving entities.
- Tool: list_cases (Remote or Local).
- Filter: description="*ENTITY_VALUE*" AND status="OPENED".
- Store ${ENTITY_RELATED_CASES}.

Read the full file on GitHub · 98 lines

Changes

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 · 98 lines · 30 tokens per session scan A c8e91763c7d4

Subscribe to this mod's changes

secops-triage is a skill published in the GitHub repository google/mcp-security (522 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,250 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.

Productivity Research Security security_operations

secops-triage