agentleFS
Sign inStart free
MELJOESTEINMELJOESTEIN/agentic-devsecops-kit/.claude/skills/threat-model/SKILL.md

threat-model

Skill0 starsChanged 56 days agoMITView on GitHub

Produire ou mettre à jour le threat model STRIDE du projet (docs/security/threat-model.md) à partir de l'architecture réelle, puis en dériver des actions priorisées. À utiliser avant une mise en production, après un changement d'architecture, ou quand l'utilisateur demande "quelles sont les menaces", "STRIDE", "modélise les risques".

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 10 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

  • mbwsimsSkill

    test-plan

    This skill should be used when the user asks to "plan tests", "what should I test", "what tests do I need", "test plan for", "testing strategy for", "test matrix for", "what cases should I cover", "help me plan tests", mentions "/test-plan", or wants to understand what tests are needed before writing any test code.

    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

The file

Create a free account to mount
Files
SKILL.md

/threat-model — Modéliser les menaces

Étapes

  1. Inventaire des sources : lister les fichiers d'architecture présents (docker-compose*.yml, infra/, k8s/, workflows CI, routes/contrôleurs, config auth). Signaler ce qui manque plutôt que l'inventer.
  2. Déléguer au sous-agent threat-modeler avec cette liste : il produit le DFD, le tableau STRIDE avec contrôles existants cités (fichier) et gaps, et écrit docs/security/threat-model.md.
  3. Contre-relecture (obligatoire, c'est la validation humaine assistée) : relire le tableau produit et vérifier au moins
    • qu'aucun « gap » ne correspond à un contrôle déjà présent dans le code (chercher dans le repo),
    • qu'aucune menace n'est hors sujet pour cette architecture,
    • que chaque gap a une mitigation et une preuve. Corriger le fichier si nécessaire et noter les corrections apportées à l'analyse.
  4. Plan d'action : les 3 à 5 gaps prioritaires sous forme d'issues (titre, risque, mitigation, preuve, effort), à proposer à l'utilisateur — ne pas les implémenter dans ce workflow.
  5. Traçabilité : entrée dans docs/security/ai-log.md (ce que l'analyse IA a bien vu, ce qu'il a fallu corriger).

Rappels

Un threat model est vivant : dater le document et lister les hypothèses. Le refaire à chaque nouvelle frontière de confiance (nouveau service, nouvelle intégration, exposition publique).

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