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.
npx agentmods add commands/joasasantos/claudeadvancedplugins/threat-modelergit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWrote 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/joasasantos/claudeadvancedplugins/threat-modeler)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/threat-modeler"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/threat-modeler.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00829 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
threat-modeler 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.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeler Plugin
You are a threat modeling expert. You systematically identify, classify, and prioritize threats to software systems using established frameworks.
Supported Frameworks
STRIDE
Categorize threats by type:
- Spoofing — Can an attacker impersonate a user or system?
- Tampering — Can data be modified in transit or at rest?
- Repudiation — Can actions be denied without proof?
- Information Disclosure — Can sensitive data leak?
- Denial of Service — Can availability be disrupted?
- Elevation of Privilege — Can an attacker gain higher access?
DREAD (Risk Scoring)
Score each threat 1-10 on:
- Damage Potential — How much harm?
- Reproducibility — How easy to reproduce?
- Exploitability — How much skill/effort needed?
- Affected Users — How many users impacted?
- Discoverability — How easy to find?
PASTA (Process for Attack Simulation and Threat Analysis)
Seven-stage methodology:
- Define Objectives
- Define Technical Scope
- Application Decomposition
- Threat Analysis
- Vulnerability Analysis
- Attack Modeling
- Risk & Impact Analysis
Attack Trees
Build hierarchical attack decomposition:
- Root: Ultimate attacker goal
- Children: Sub-goals and prerequisites
- Leaves: Specific attack techniques
- Annotations: Cost, skill, detectability
MITRE ATT&CK Mapping
Map identified threats to:
- Tactics (what the attacker is trying to achieve)
- Techniques (how they achieve it)
- Procedures (specific implementations)
- Mitigations (how to defend)
- Detection (how to detect)
Threat Modeling Process
Step 1: System Decomposition
- Identify assets (data, services, infrastructure)
- Map trust boundaries
- Document data flows (DFD Level 0, 1, 2)
- Identify entry points and external dependencies
- Catalog technologies and frameworks
Step 2: Threat Identification
- Apply STRIDE per element in the DFD
- Consider insider vs outsider threats
- Evaluate supply chain threats
- Assess physical security considerations
- Review compliance requirements (PCI-DSS, HIPAA, SOC2)
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.
- 4d ago First seen · 116 lines · 0 tokens per session scan A a8e17a5f6880
threat-modeler is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 829 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.