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/jaskaranhundal/usap-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/commands/jaskaranhundal/usap-skills/orchestrate)<a href="https://agentmods.dev/commands/jaskaranhundal/usap-skills/orchestrate"><img src="https://agentmods.dev/badge/commands/jaskaranhundal/usap-skills/orchestrate/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/commands/jaskaranhundal/usap-skills/orchestrate"><img src="https://agentmods.dev/badge/commands/jaskaranhundal/usap-skills/orchestrate.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.00052 | $0.01616 |
| Opus 5 | $0.00026 | $0.00808 |
| Sonnet 5 | $0.00010 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
orchestrate 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the full USAP 4-agent orchestration chain against the Perfect Storm scenario.
Read tests/scenarios/nation-state-apt-crisis.json now — you will use it throughout.
Read tests/mocks/orchestration-chain-mock.json now — you will compare against it at the end.
Operate each agent in sequence. Each agent reads its own file, adopts its persona, applies its workflow, and produces output that the next agent consumes. Show a clear separator between each agent's section.
Agent 1 of 4 — cs-security-analyst (AT Workflow)
Read agents/security/cs-security-analyst.md in full.
Adopt the Alex persona (Tier 2 SOC, 12y). Apply the AT (Alert Triage) workflow to the Perfect Storm scenario.
Produce abbreviated output focused on the handoff payload:
- Top-5 alert priority signals (ranked, DDoS noise suppressed)
- Kill chain stage mapping (6 stages, all 8 vectors assigned)
- Two threat actor entries (nation-state APT + ransomware gang, clearly differentiated)
- SEV-1 declaration
- Routing decision:
next_agents: ["cs-incident-responder", "cs-ciso-advisor"]with justification - Prerequisite checks: all 7 UNKNOWN fields as PREREQUISITE_UNVERIFIED
- Sequenced containment plan (ransomware → APT → insider → supply chain)
- Regulatory flags (GDPR 72h + SEC 4-day)
human_approval_required: true
Show the handoff payload passed to Agent 2 (the fields cs-incident-responder will consume).
Agent 2 of 4 — cs-incident-responder (CO Workflow)
Read agents/security/cs-incident-responder.md in full.
Adopt the Jordan persona (IR Lead, 14y). Consume the Agent 1 handoff payload as your incident input.
Apply the CO (Active Containment) workflow. Produce:
- Formal SEV-1 incident declaration with incident ID and timestamp
- SLA clock: detection-to-containment target, eradication target, recovery target
- Containment action intents in correct sequence (ransomware first — all as intent blocks, no CLI)
- Evidence preservation order: collect C2 artifacts from DC-002 BEFORE evicting APT implants
- Forensic collection plan for compromised hosts (intent blocks only)
- Inherited prerequisite checks — propagate all 7 UNKNOWN fields, do not resolve by assumption
- Rollback plan for each isolation action
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.
- 9d ago First seen · 139 lines · 52 tokens per session scan A 3767f79723e1
orchestrate is a command published in the GitHub repository jaskaranhundal/usap-skills (4 stars, last pushed 4d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,616 once invoked, about $0.0003 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.