Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aiocean/claude-plugins/plugin install aio-advisorWrote 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/skills/aiocean/claude-plugins/aio-threat-models)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-threat-models"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-threat-models.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.1 | $0.00084 | $0.04092 |
| Opus 5 | $0.00042 | $0.02046 |
| Sonnet 5 | $0.00017 | $0.00818 |
| Haiku 4.5 | $0.00008 | $0.00409 |
Grade A, and why
aio-threat-models 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 6d 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeling Framework Advisor
"Threat modeling is analyzing representations of a system to highlight concerns about security and privacy characteristics." — Threat Modeling Manifesto (2020)
Workflow: How to Use This Skill
When this skill is triggered, follow these five steps. Do NOT just dump framework descriptions — actively guide the user through their specific threat modeling task.
Step 1: ASK — Understand the System
Before selecting frameworks, gather essential context (if not already clear):
- What system is being threat modeled? (new design, existing system, specific feature)
- Is it primarily a security, privacy, or both concern?
- What domain? (web app, mobile, cloud-native, microservices, AI/ML, IoT, cyber-physical)
- Who processes the output? (developers, SOC, compliance, regulators, executives)
- What lifecycle phase? (requirements, design, implementation, operations, incident review)
- Regulatory context? (GDPR, HIPAA, PCI DSS, EU AI Act, SOC 2, etc.)
- Team expertise level? (beginners, security-experienced, dedicated security team)
If the user's message already contains enough context, proceed directly to Step 2.
Step 2: SEARCH — Find Relevant Frameworks
First, run semantic search with the user's problem as the query to find the most relevant frameworks. Then cross-reference with the routing table below.
TM="${CLAUDE_PLUGIN_ROOT}/skills/aio-threat-models/scripts"
npx tsx "$TM/search-models.ts" "<user's threat modeling problem>" --top 5 --json
Read the full markdown file for each top result before proceeding. Use the routing table as a secondary guide:
| Context | Start With |
|---|---|
| Starting fresh, new web/app system | Shostack 4Q + STRIDE + DFD |
| Privacy-sensitive system (PII/PHI) | LINDDUN (parallel to STRIDE) + DPIA |
| Regulated finance/healthcare | PASTA + STRIDE + DPIA (if PII) |
| Enterprise DevSecOps at scale | VAST (or IriusRisk) + Continuous TM |
| Organizational risk assessment | OCTAVE Allegro |
| High-value attack scenario | Attack Trees |
| Creative threat discovery, diverse team | Security Cards + PnG (consider hTMM) |
| Requirements-phase threat modeling | hTMM (Cards + PnG + SQUARE) |
| ML/AI system | OWASP LLM Top 10 + MITRE ATLAS + NIST AI RMF + NIST AI 100-2 |
| Cloud-native / K8s | Shared Responsibility + CNCF 4-layer + K8s Threat Matrix |
| CTI / incident analysis | Diamond Model + Kill Chain / UKC + MITRE ATT&CK |
| Agile sprint integration | Threat Model as Code (pytm / Threagile) + Continuous TM |
| Access control system | Trike (requirements matrix) |
| Scoring identified threats | CVSS or bug bars (DO NOT use DREAD — deprecated) |
| AI-phase adversarial ML rigor | NIST AI 100-2 taxonomy |
What ships with it
34 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/.gitignore 14 B
- scripts/build-embeddings.ts 2.7 KB runs code
- scripts/embeddings.json 289 KB
- scripts/list-models.sh 3.0 KB runs code
- scripts/package-lock.json 38 KB
- scripts/package.json 143 B
- scripts/search-models.ts 3.4 KB runs code
- volume-1-foundations/01-shostack-4-questions.md 3.3 KB
- volume-1-foundations/02-dfd-trust-boundaries.md 3.9 KB
- volume-1-foundations/03-threat-modeling-manifesto.md 4.0 KB
- volume-2-core-frameworks/01-stride.md 4.0 KB
- volume-2-core-frameworks/02-dread.md 3.7 KB
- volume-2-core-frameworks/03-pasta.md 3.7 KB
- volume-2-core-frameworks/04-octave-allegro.md 3.9 KB
- volume-2-core-frameworks/05-trike.md 3.7 KB
- volume-2-core-frameworks/06-vast.md 3.8 KB
- volume-3-attacker-centric/01-attack-trees.md 4.3 KB
- volume-3-attacker-centric/02-persona-non-grata.md 4.4 KB
- volume-3-attacker-centric/03-security-cards.md 4.3 KB
- volume-3-attacker-centric/04-htmm.md 4.4 KB
- volume-4-attack-patterns/01-cyber-kill-chain.md 3.9 KB
- volume-4-attack-patterns/02-unified-kill-chain.md 3.7 KB
- volume-4-attack-patterns/03-mitre-attack.md 4.5 KB
- volume-4-attack-patterns/04-diamond-model.md 4.1 KB
- volume-4-attack-patterns/05-capec.md 4.4 KB
- volume-5-privacy/01-linddun.md 5.0 KB
- volume-5-privacy/02-gdpr-dpia.md 5.1 KB
- volume-6-ai-ml/01-owasp-llm-top10.md 4.9 KB
- volume-6-ai-ml/02-mitre-atlas.md 4.6 KB
- volume-6-ai-ml/03-nist-ai-rmf.md 4.6 KB
- volume-6-ai-ml/04-nist-ai-100-2.md 5.1 KB
- volume-7-cloud-devsecops/01-cloud-threat-modeling.md 5.3 KB
- volume-7-cloud-devsecops/02-kubernetes-threat-matrix.md 5.2 KB
- volume-7-cloud-devsecops/03-continuous-threat-modeling.md 5.8 KB
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.
- 6d ago First seen · 329 lines · 84 tokens per session scan A 95679323f9fc
aio-threat-models is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 4,092 once invoked, about $0.0004 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 skills, from other repositories
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
self-assessment
Interactive skill assessment with personalized learning path generation.