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 skills add The-AI-Directory-Company/agents-and-skills --skill threat-model-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/skills/the-ai-directory-company/agents-and-skills/threat-model-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/threat-model-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/threat-model-writing/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/skills/the-ai-directory-company/agents-and-skills/threat-model-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/threat-model-writing.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.00038 | $0.01565 |
| Opus 5 | $0.00019 | $0.00783 |
| Sonnet 5 | $0.00008 | $0.00313 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
threat-model-writing 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 8d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Model Writing
Before you start
Gather the following information. If any is missing, ask the user before proceeding:
- System description — What does the system do? Architecture type (monolith, microservices, serverless)?
- Data sensitivity — PII, financial, health, credentials, intellectual property?
- Trust boundaries — Where does trusted meet untrusted? Browser-to-API, service-to-database, internal-to-third-party?
- Deployment environment — Cloud provider, on-prem, hybrid? Network boundaries?
- Compliance requirements — SOC 2, HIPAA, PCI-DSS, GDPR, or none?
- Existing security controls — Authentication, authorization, encryption, and monitoring already in place?
If the user provides only a feature name ("we built a payments API"), push back and ask for architecture details, data flows, and trust boundaries.
Threat model template
Every section is required unless explicitly marked optional.
Title
[System Name] — STRIDE Threat Model
1. System Overview (3-5 sentences)
Describe purpose, architecture, and key data flows. List major components and how they communicate:
User Browser → (HTTPS) → API Gateway → (gRPC) → Auth Service → (TLS) → Database
→ (gRPC) → Payment Service → (TLS) → Stripe API
2. Assets
Enumerate what an attacker would target. For each asset, state CIA requirements:
| Asset | Confidentiality | Integrity | Availability | Notes |
|---|---|---|---|---|
| User credentials | Critical | Critical | High | Hashed with bcrypt, salted |
| Payment tokens | Critical | Critical | High | Tokenized via Stripe, never stored raw |
3. Threat Actors
Identify who might attack the system and their capabilities. Tailor to the system — a B2B internal tool has different actors than a public consumer API.
- External unauthenticated — Script kiddies, automated scanners. Low skill, high volume.
- External authenticated — Malicious users with valid accounts. Medium skill, targeted.
- Insider — Employees or contractors with system access. High skill, privileged.
- Supply chain — Compromised dependencies or third-party services.
What ships with it
4 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.
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.
- 8d ago First seen · 131 lines · 38 tokens per session scan A 6b1c34b6b226
threat-model-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,565 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.