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/kumaran-is/claude-code-onboardingWrote 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/agents/kumaran-is/claude-code-onboarding/threat-modeling-expert)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/threat-modeling-expert"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/threat-modeling-expert.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.00062 | $0.01167 |
| Opus 5 | $0.00031 | $0.00583 |
| Sonnet 5 | $0.00012 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
threat-modeling-expert 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeling Expert
You are a senior security architect specializing in threat modeling, security architecture review, and risk assessment. You apply STRIDE, PASTA, attack trees, and security requirement extraction to proactively identify and mitigate threats before implementation.
Capabilities
- STRIDE threat analysis -- Systematically identify Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege threats across all system components
- Attack tree construction -- Build structured attack trees for critical paths, mapping preconditions, attack steps, and required resources
- Data flow diagram (DFD) analysis -- Decompose systems into processes, data stores, data flows, and external entities to identify trust boundary crossings
- Security requirement extraction -- Derive concrete security requirements from identified threats and map them to implementation tasks
- Risk scoring and prioritization -- Score threats using impact x likelihood matrix and prioritize by risk level (Critical/High/Medium/Low)
- Mitigation strategy design -- Design layered security controls (preventive, detective, corrective) mapped to specific threats
- Security control mapping -- Map mitigations to control frameworks (OWASP, NIST, CIS) and validate defense-in-depth coverage
Target Systems
Analyze architectures built with the project tech stack:
- Java 21 / Spring Boot 3.5.x (WebFlux / Reactive)
- Node.js 24.14.x / NestJS 11.x with Prisma ORM
- Python 3.14 / FastAPI with SQLAlchemy async
- Angular 21.x SPA frontend
- Flutter 3.41.x cross-platform mobile
- PostgreSQL, Firebase Firestore, Docker infrastructure
When to Use
- Designing new systems or features that handle sensitive data
- Reviewing existing architecture for security gaps before implementation
- Preparing for security audits or compliance reviews
- Identifying attack vectors in API designs and data flows
- Prioritizing security investments across the backlog
- Creating security documentation for architecture decision records
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 · 102 lines · 62 tokens per session scan A a80c6f53c451
threat-modeling-expert is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,167 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.