incident-commander

incident-commander is a skill for Claude Code from jaskaranhundal/usap-skills. It costs 0 tokens per session (11 once invoked), scanned A, original, Apache-2.0.

An incident-response coordination guide for directing several agents during a security incident. An incident commander sets severity, assigns work, and coordinates decisions while other responders investigate and contain the problem.

In plain words
What is it for?
Use it to declare incident severity, assign investigation and response tracks, record decisions, and coordinate work during a breach or other active security event.
Why use it?
It provides a clear decision structure when events are moving quickly and many response tasks need coordination. It also separates coordination from actions that require security leadership approval.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the usap-skills plugin — 87 skills, 7 commands, 1 plugin shipped together

Good fit Use it to declare incident severity, assign investigation and response tracks, record decisions, and coordinate work during a breach or other active security event.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jaskaranhundal/usap-skills/incident-commander
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.

Any agent
npx skills add jaskaranhundal/usap-skills --skill incident-commander
Clone the repo
git clone --depth 1 https://github.com/jaskaranhundal/usap-skills

Made for: Claude Code.

Or install usap-skills, the plugin that ships this one along with the rest of its 87 skills, 7 commands, 1 plugin.

Wrote 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.

agentmods badge for incident-commander

README.md
[![agentmods](https://agentmods.dev/badge/skills/jaskaranhundal/usap-skills/incident-commander/github.svg)](https://agentmods.dev/skills/jaskaranhundal/usap-skills/incident-commander)
Your own site
<a href="https://agentmods.dev/skills/jaskaranhundal/usap-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/jaskaranhundal/usap-skills/incident-commander/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.

agentmods 80×15 button for incident-commander

Your own site · 80×15
<a href="https://agentmods.dev/skills/jaskaranhundal/usap-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/jaskaranhundal/usap-skills/incident-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 11 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00011
Opus 5 $0.00000 $0.00005
Sonnet 5 $0.00000 $0.00002
Haiku 4.5 $0.00000 $0.00001

Measured 4d ago against content hash 29d4547b0116, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

incident-commander 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/incident-commander_tool.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/incident-commander/SKILL.md · 1 lines

What it actually says

../../../response/incident-commander/SKILL.md

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 4d ago Changed · -211 lines · -35 tokens per session 29d4547b0116
  2. 6d ago First seen · 212 lines · 35 tokens per session scan A 65adabec3163

Subscribe to this mod's changes

incident-commander is a skill published in the GitHub repository jaskaranhundal/usap-skills (4 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 11 tokens. 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-09-05.

Related

Other skills, from other repositories

contact-template

Contact / communications plan generator — primary operator, escalation chain, abort signal recipient, external SOC endpoint, blackout windows.

MingyiSecLab/Mingyi-Atlas · 26 tokens

building-vulnerability-dashboard-with-defectdojo

Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.

26zl/cybersec-toolkit · 37 tokens

Governance

Organizational governance for PAI agent infrastructure — budget controls, approval gates, goal ancestry, org chart visualization, standing orders, config portability, workspaces, and task locking. USE WHEN user mentions budget, spending, approval, governance, org chart, goals, standing orders, heartbeat, export…

CarbeneAI/Forge · 76 tokens

nuclei

Nuclei CLI parameter reference and usage patterns - YAML-template vulnerability scanning, target input modes, template filters, output formats, rate limits, ProjectDiscovery dashboard upload, and common scan commands.

MingyiSecLab/Mingyi-Atlas · 42 tokens

final-report

Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.

MingyiSecLab/Mingyi-Atlas · 28 tokens

deserialization-exploitation

Insecure deserialization — RCE via malicious serialized objects in Java (ysoserial), PHP (PHPGGC), .NET (ysoserial.net), and Python (pickle). Covers gadget chain selection, payload generation, and injection into cookies, POST bodies, ViewState, and API endpoints.

MingyiSecLab/Mingyi-Atlas · 65 tokens