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.
git clone --depth 1 https://github.com/briiirussell/cybersecurity-skillsWrote 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/rules/briiirussell/cybersecurity-skills/incident-triage)<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/incident-triage"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/incident-triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/incident-triage"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/incident-triage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00147 | $0.02817 |
| Opus 5.5 | $0.00059 | $0.01127 |
| Sonnet 5.5 | $0.00029 | $0.00563 |
| Haiku 4.5 | $0.00015 | $0.00282 |
Grade A, and why
incident-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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Triage — Security Incident Response
Guide rapid triage and initial response to security incidents. Follow NIST SP 800-61 Rev. 3 (April 2025), which
replaced Rev. 2's four-phase lifecycle with the CSF 2.0 Functions: Govern, Identify and Protect are the preparation that
happens before an incident; Detect, Respond and Recover are the response. This skill covers the first hours — Detect
through the start of Respond — and hands off the rest. Each step names the CSF 2.0 outcomes it produces, so the report
maps straight onto the organization's CSF profile (see csf-mapping).
Cross-references: siem-detection for the rules that produced the alert this triage is responding to, disk-forensics for deeper disk and memory analysis once a host is contained, breach-patterns for the post-incident pattern extraction that hardens against recurrence, soc-operations for the operational layer above this skill (runbooks, escalation, handoff), security-comms for the stakeholder / customer notifications the response generates, privacy-engineering / hipaa-audit / pci-audit for the regulatory-clock determination when personal data, PHI, or cardholder data is involved, ai-risk-management for AI-specific incident classes (model failure, fairness drift, jailbreak exploitation in production), agent-supply-chain-audit when the suspected entry point is an AI coding-agent extension (a skill, plugin, hook or MCP server), log-watch for the scheduled log review that often raises the first alert on small teams, secrets-audit for its exfiltration-collector domain list (webhook.site, requestbin, ngrok, Discord / Telegram / Slack webhooks) to check egress logs against when credential theft is suspected.
Authorization
Act only for the system owner or the incident lead, on systems in scope. The read-only commands below (process, network, user and file listings) are pre-approved. Every containment action — blocking, isolating, disabling an account, stopping a service — changes production: name the action and its blast radius, and get the incident lead's go-ahead before running it. Never touch systems outside the declared scope, even if indicators point there; report them instead.
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.
- today Changed · +78 lines · +67 tokens per session 2c69c0a0f0fa
- 1mo ago First seen · 159 lines · 80 tokens per session scan A b8941406942f
incident-triage is a cursor rule published in the GitHub repository briiirussell/cybersecurity-skills (435 stars, last pushed today), licensed MIT. It adds 147 tokens to every session and 2,817 once invoked, about $0.0006 per session on Opus 5.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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.