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/RedHatProductSecurity/agentic-threat-modelingWrote 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/redhatproductsecurity/agentic-threat-modeling/threat-model-review)<a href="https://agentmods.dev/commands/redhatproductsecurity/agentic-threat-modeling/threat-model-review"><img src="https://agentmods.dev/badge/commands/redhatproductsecurity/agentic-threat-modeling/threat-model-review/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/redhatproductsecurity/agentic-threat-modeling/threat-model-review"><img src="https://agentmods.dev/badge/commands/redhatproductsecurity/agentic-threat-modeling/threat-model-review.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.00025 | $0.00386 |
| Opus 5 | $0.00013 | $0.00193 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
threat-model-review 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.
What it actually says
Invoke the threat-model-review skill.
Find and review an existing threat model:
- Locate THREAT_MODEL.md (in the repo root, or at the path specified by the user)
- Parse its contents — threats, mitigations, assumptions, scope
- Analyze what has changed in the codebase since the threat model was written
- Identify:
- Stale threats: threats that no longer apply due to code changes or mitigations implemented
- New attack surface: new endpoints, components, data flows, or integrations not covered by the existing threat model
- Drift: assumptions that are no longer valid
- Open mitigations: recommended mitigations that haven't been implemented yet
- Produce an update report with recommended changes to the threat model
- After presenting the review findings, offer to apply the changes directly:
"Would you like me to apply these changes to the threat model now? I can update the THREAT_MODEL.md to incorporate the findings — removing stale threats, adjusting risk levels, and adding coverage for new attack surface. You'll be able to review the changes before they're finalized." If the user agrees, apply changes following update mode rules: preserve existing threat and hardening-recommendation IDs (T-NNN and H-NNN alike, never renumber), move removed threats or resolved/no-longer-relevant hardening recommendations to Deprioritized Threats with removal reason and date, preserve human-written edits, and append an Update History entry to the provenance section.
Arguments from user: $ARGUMENTS
If no THREAT_MODEL.md is found, suggest running /threat-model to create one.
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 · 25 lines · 25 tokens per session scan A 207bd9994bba
threat-model-review is a command published in the GitHub repository RedHatProductSecurity/agentic-threat-modeling (4 stars, last pushed 29d ago), licensed Apache-2.0. It adds 25 tokens to every session and 386 once invoked, about $0.0001 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.