agentleFS
Sign inStart free
sarveshtalelesarveshtalele/devcrew/.claude/skills/threat-model/SKILL.md

threat-model

Skill1 starsChanged 3 months agoMITView on GitHub

STRIDE + OWASP LLM threat model for a component. Run BEFORE coding anything touching auth, payments, health data, file upload, deserialization, or a model call.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use vuln-scan, supply-chain-review and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    vuln-scan

    Static source-code vulnerability scan. Reads a target directory (and THREAT_MODEL.md if present), spawns parallel review subagents per focus area, and writes VULN-FINDINGS.json + .md for /triage to consume. Read-only — no building, running, or network. For execution-verified crashes, use vuln-pipeline instead. Use when asked to "scan for vulns", "review this code for security issues", "find bugs in <dir>", or as the step between /threat-model and /triage.

    Also in 5 projects that use this

  • MesteriisSkill

    supply-chain-review

    Reviews lockfiles, installers, provenance, CI permissions, dependency confusion, artifacts, registries, and publishing.

    Also in 3 projects that use this

  • AnthropicSkill

    patch

    Generate candidate fixes for verified security findings. Consumes

    Also in 4 projects that use this

  • mbwsimsSkill

    orbit

    Run for repo-wide or diff-wide readiness sweeps: "/orbit", "/orbit pr", "/orbit deep", "/orbit quick", "audit this project", "project-wide review", "is this PR ready overall", or "combined security, tests, codebase, evolution, and instruction review". Use this for broad multi-system assessment, not for a single-file review or a one-domain question.

    Also in 3 projects that use this

  • Sagargupta16Skill

    dependency-audit

    Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.

    Also in 4 projects that use this

  • patrickserranoSkill

    performance-audit

    Audit and improve SwiftUI runtime performance. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Threat-model: $ARGUMENTS

Delegate to the security-engineer agent. Output to docs/design/threat-model-<component>.md from templates/threat-model.md.

  1. Draw the boundaries. Data flow diagram: entities, processes, stores, and every trust boundary crossed. Threats live on boundaries.
  2. STRIDE per boundary — Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege.
  3. Per threat: asset at risk · entry point · concrete exploit path · existing control · gap · mitigation · the test that proves the mitigation. A threat without an exploit path is speculation — cut it.
  4. Data classes: which PII/PHI/CHD crosses which boundary, and is it encrypted, minimized, and absent from logs?
  5. If an LLM is involved, add the OWASP LLM Top 10 pass: prompt injection (untrusted-data framing, tool allowlist), insecure output handling (schema-parse before use), sensitive disclosure (redact before prompt), excessive agency (scoped identity, human confirm on irreversible actions), unbounded consumption (rate + token limits), supply chain (pinned model IDs), poisoning (corpus provenance), guardrails (input/output classifiers with logged blocks).
  6. File every unmitigated gap as a card in trackers/security.md with a severity. Nothing gets closed by assertion.

Rank by exploitability × impact. Fix Critical and High before stage 10.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free