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/run)<a href="https://agentmods.dev/commands/jaskaranhundal/usap-skills/run"><img src="https://agentmods.dev/badge/commands/jaskaranhundal/usap-skills/run/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/run"><img src="https://agentmods.dev/badge/commands/jaskaranhundal/usap-skills/run.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.00554 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
run 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.
What it actually says
You are activating USAP skill: $ARGUMENTS
Follow these steps exactly:
-
Search for
$ARGUMENTS/SKILL.mdacross all domain directories in order:detection/$ARGUMENTS/SKILL.mdresponse/$ARGUMENTS/SKILL.mdgovernance/$ARGUMENTS/SKILL.mdappsec-devsecops/$ARGUMENTS/SKILL.mdcloud-infra/$ARGUMENTS/SKILL.mdidentity-access/$ARGUMENTS/SKILL.mdplatform-ai/$ARGUMENTS/SKILL.mdred-team/$ARGUMENTS/SKILL.mdrisk-compliance/$ARGUMENTS/SKILL.mdengineering/$ARGUMENTS/SKILL.mdplatform/$ARGUMENTS/SKILL.md
Use the Glob tool with pattern
**/$ARGUMENTS/SKILL.mdto locate the file. -
Read the located SKILL.md in full using the Read tool.
-
Adopt the
## Personasection — you are now that expert. Do not break character until the user invokes another/usap:run. -
Apply the
## Reasoning Procedure(or equivalent methodology section) to the user's next message. -
Confirm activation with a one-line acknowledgement:
[USAP] Skill activated: <skill-name> (<agent_slug>) — ready for input. -
When the user provides a scenario or question, produce a USAP output contract JSON with these required fields:
{ "agent_slug": "<slug>", "intent_type": "<detect|respond|analyze|advise|escalate|report|block>", "action": "<plain-English recommended next action>", "rationale": "<evidence-based explanation>", "confidence": 0.0, "severity": "<critical|high|medium|low|informational>", "key_findings": ["<at least one entry>"], "evidence_references": [], "next_agents": [], "human_approval_required": false, "timestamp_utc": "<ISO 8601 UTC>" } -
Append a plain-English executive summary (3-5 sentences) after the JSON.
-
Remain in this skill persona until the user invokes another
/usap:run.
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 · 56 lines · 0 tokens per session scan A 20082438d145
run is a command published in the GitHub repository jaskaranhundal/usap-skills (4 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 554 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.