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 skills/backspace-shmackspace/claude-devkit/threat-model-gatenpx skills add backspace-shmackspace/claude-devkit --skill threat-model-gategit 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-gate)<a href="https://agentmods.dev/skills/backspace-shmackspace/claude-devkit/threat-model-gate"><img src="https://agentmods.dev/badge/skills/backspace-shmackspace/claude-devkit/threat-model-gate.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.00039 | $0.03106 |
| Opus 5 | $0.00019 | $0.01553 |
| Sonnet 5 | $0.00008 | $0.00621 |
| Haiku 4.5 | $0.00004 | $0.00311 |
Grade A, and why
threat-model-gate 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 5d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Model Gate
Overview
Security cannot be added later. Features that touch user data, system boundaries, or trust relationships require threat modeling during planning — not after code is written.
Core Principle
Every feature that handles user data, authentication, or system boundaries requires explicit threat modeling before implementation.
"We'll secure it in the next sprint" is a commitment that never gets honored. The cost of retrofitting security is 10x the cost of designing it in. Threat modeling during planning is the minimum viable security practice.
When to Activate
Apply this gate when planning involves any of the following:
Authentication and Identity
- Login flows, session management, token issuance or validation
- Multi-factor authentication, SSO, OAuth, OIDC, SAML
- Password storage, credential management, account recovery
Authorization and Access Control
- Role-based or attribute-based access control (RBAC, ABAC)
- Resource ownership and sharing models
- Admin capabilities, privilege escalation paths
- API key or service account permissions
Data Handling
- PII collection, storage, or transmission
- Payment card data, health records, or regulated data categories
- Encryption at rest or in transit
- Data retention, deletion, or export features
API Design
- Public-facing endpoints, webhooks, or callbacks
- Inter-service communication with trust implications
- Rate limiting and abuse prevention
- Input validation and output encoding boundaries
Cryptography
- Key generation, storage, or rotation
- Algorithm selection (hashing, signing, encryption)
- Certificate management, mTLS
- Secure random number generation
Network and Infrastructure
- Firewall rules, network segmentation, VPN configurations
- Load balancer, reverse proxy, or CDN configurations
- Container networking, service mesh, Kubernetes network policies
- DNS, TLS termination, certificate pinning
The Threat Modeling Checklist
Work through these four areas before committing to an implementation approach:
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.
- 5d ago First seen · 303 lines · 39 tokens per session scan A 999dbc5370b6
threat-model-gate is a skill published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 3,106 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-08-30.
Other skills, from other repositories
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.