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/readme)<a href="https://agentmods.dev/commands/jaskaranhundal/usap-skills/readme"><img src="https://agentmods.dev/badge/commands/jaskaranhundal/usap-skills/readme/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/readme"><img src="https://agentmods.dev/badge/commands/jaskaranhundal/usap-skills/readme.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.00000 | $0.01259 |
| Opus 5 | $0.00000 | $0.00629 |
| Sonnet 5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
README 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 10d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
USAP Slash Commands
Claude Code slash commands for the Unified Security Agent Platform (USAP). These commands let you load any USAP skill as a live LLM persona and run structured compliance tests — all inside a Claude Code session.
Commands
| Command | Usage | Purpose |
|---|---|---|
/usap:run |
/usap:run <skill-slug> |
Load any SKILL.md and activate it as your operating persona |
/usap:test |
/usap:test <skill-slug> |
Run the FortiGate zero-day scenario + 6-problem compliance scorecard |
/usap:compare |
/usap:compare |
Before/after v1 vs v2 comparison for zero-day-response |
/usap:challenge |
/usap:challenge |
Run cs-security-analyst against the Perfect Storm 8-vector crisis + 12-check mock scorecard |
/usap:fortigate |
/usap:fortigate |
Run cs-security-analyst (AT + CA workflows) against the Fintech FortiGate zero-day + 7-task scorecard |
/usap:orchestrate |
/usap:orchestrate |
Run full 4-agent chain (analyst → responder → CISO → program-manager) against Perfect Storm |
Quick Start
# Activate a skill and ask it a question
/usap:run zero-day-response
> We have a FortiOS CVSS 9.8 zero-day with no patch. What do we do?
# Run the compliance test (FortiGate scenario, 6 checks)
/usap:test zero-day-response
# See the before/after fix comparison
/usap:compare
# Run cs-security-analyst against the world's hardest scenario (12-check mock comparison)
/usap:challenge
# Run cs-security-analyst (AT + CA) against the Fintech FortiGate zero-day (7-task scorecard)
/usap:fortigate
# Run the full 4-agent orchestration chain against the Perfect Storm
/usap:orchestrate
How It Works
Each .md file in this directory is a Claude Code slash command. When invoked, Claude reads the command body and follows the instructions — including using the Read and Glob tools to load the target SKILL.md.
The skill's ## Persona and ## Reasoning Procedure sections become Claude's active operating context. All output follows the USAP output contract (JSON + executive summary).
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.
- 10d ago First seen · 89 lines · 0 tokens per session scan A 7b5d9660a39c
README is a command published in the GitHub repository jaskaranhundal/usap-skills (4 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,259 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-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.