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 backspace-shmackspace/claude-devkit --skill threat-modelgit clone --depth 1 https://github.com/backspace-shmackspace/claude-devkitWrote 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/backspace-shmackspace/claude-devkit/threat-model)<a href="https://agentmods.dev/skills/backspace-shmackspace/claude-devkit/threat-model"><img src="https://agentmods.dev/badge/skills/backspace-shmackspace/claude-devkit/threat-model/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/backspace-shmackspace/claude-devkit/threat-model"><img src="https://agentmods.dev/badge/skills/backspace-shmackspace/claude-devkit/threat-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 696 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00070 | $0.12680 |
| Opus 5.5 | $0.00028 | $0.05072 |
| Sonnet 5.5 | $0.00014 | $0.02536 |
| Haiku 4.5 | $0.00007 | $0.01268 |
Grade A, and why
threat-model 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 1mo 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 — 1,311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeling
Structured threat identification and risk assessment for software systems using STRIDE threat categorization and DREAD risk rating, producing both machine-readable Open Threat Model (OTM) JSON and human-readable markdown reports.
Core Principles
-
Risk-First: Focus analysis effort on high-value assets and exposed trust boundaries. Not every component warrants equal analysis depth -- prioritize by data sensitivity and exposure.
-
Evidence-Based: Every identified threat must be backed by specific data flows, components, and trust zone crossings. A threat without a concrete scenario is speculation, not analysis.
-
Repeatable: The same project context must yield structurally consistent models regardless of which analyst or AI assistant performs the analysis. The three-phase workflow and verification checklist enforce this constraint.
-
Dual-Output: Always produce both OTM JSON (for toolchain integration) and a markdown report (for human review). Neither is a subset of the other -- both must be complete.
-
Honest: Explicitly state scope limits, assumptions, confidence levels, and what was NOT analyzed. A threat model that overstates its coverage is worse than one that honestly declares its boundaries.
A note on DREAD. Microsoft deprecated DREAD in 2008 in favor of CVSS-based bug bar approaches. This skill retains DREAD for three reasons: (1) CVSS scores vulnerabilities, not threats -- DREAD is purpose-built for threat modeling; (2) DREAD's five-axis model is simpler and more practical for systematic analysis than CVSS's base/temporal/ environmental scoring; (3) STRIDE-GPT and other modern threat modeling tools validate DREAD's continued utility. Organizations that require CVSS should map DREAD outputs to their internal risk scale after completing the threat model.
Output sensitivity. Threat model artifacts contain detailed descriptions of exploitable weaknesses, unmitigated threats, and attack scenarios. Treat all outputs (OTM JSON, markdown reports, working notes) as confidential. Store them in access-controlled repositories. Do not share threat model artifacts over unencrypted channels or in public forums. Consult your organization's data classification policy for specific handling requirements.
What ships with it
2 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.
- 1mo ago First seen · 1,311 lines · 70 tokens per session scan A c692b8aaa9a4
threat-model is a skill published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 12,680 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
architect
Produces Alon's design-doc system before code: SOURCEOFTRUTH.md, ARCHITECTUREROADMAP.md, TODOWORKFLOW.md, CLAUDE.md, plus a modular docs/architecture set for larger projects. Model first: data and invariants before framework, every invariant enforced at two boundaries, failure paths designed as deliberately as happy…
ponytail
Forces the laziest solution that actually works: YAGNI, reuse before new code, stdlib before custom, native platform before dependencies, one line before fifty. Three levels — lite (name the lazier alternative, build what's asked), full (ladder enforced, default), ultra (YAGNI extremist, challenge the requirement…
review-swarm
Local, free, multi-specialist review of a diff: parallel Claude subagents for correctness, security/trust boundaries, data/perf, architecture-altitude, ponytail-simplicity, and tests/failure-paths, each non-trivial finding adversarially verified before being kept, deduped, and ranked into a Blockers / Should-fix /…
ask-the-council
Convenes a panel of opinionated Claude advisors, each with a distinct mandate and a forbidden move so they genuinely diverge, then a Chairman synthesis that commits to one recommendation with the decisive tradeoff and the strongest dissent named.
prompt-generator
Turns a vague ask into a rigorous, grounded, token-efficient prompt for another agent or LLM: role and objective, testable done criteria, anti-hallucination and anti-tokenmaxing rules baked into the generated prompt itself, and strict agent discipline for coding-agent hand-offs.
up-to-date
Preflight sync and situational brief before repo work: fetches origin, reports ahead/behind divergence (with a no-upstream/detached-HEAD fallback), recent commits, open PRs and issues touching the work, and dirty-tree warnings, then names one recommended first action. Read-only by default — never pulls, rebases…