agentleFS
Sign inStart free
awarexoneawarexone/AXguard/threat-modeling/SKILL.md

threat-modeling

Skill17 starsChanged 47 days agoMITView on GitHub

Lightweight threat modeling for an application before deep scanning — map assets, trust boundaries, and abuse cases; feeds /axguard-audit.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before /axguard-audit on unfamiliar systems

    line 39

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Threat Modeling

Purpose

Produce a short, actionable threat model that guides which AXGuard skills and scans to run next.

When to Use

  • New codebase / first audit
  • Major feature (auth, payments, agents, file import)
  • Before /axguard-audit on unfamiliar systems

When Not to Use

  • Single-line bugfix with known sink (go straight to the class skill)

Analysis Workflow

  1. Assets: data, secrets, admin, money movement, model tools.
  2. Actors: anonymous, user, admin, attacker, malicious model/tool output.
  3. Trust boundaries: browser↔API, API↔DB, API↔cloud, agent↔tools, CI↔prod.
  4. STRIDE-lite per boundary (spoof, tamper, repudiate, info disclosure, DoS, elevation) — keep to realistic top abuses.
  5. Rank top 5 abuse cases.
  6. Map each to an AXGuard command/skill (/axguard-auth, ssrf-analysis, etc.).
  7. Hand off to axguard audit + focused skills.

Evidence Requirements

Threat models are design artifacts, not vulns. Do not report a CVE from modeling alone.

Remediation

Insecure design findings become backlog controls (authZ checks, allowlists, least privilege) tracked into remediation skills.

Related Skills

attack-surface-mapping, security-architecture-review, axguard-cso

Framework Mapping

  • OWASP A04:2021 Insecure Design

References

Research Provenance

Primary: OWASP Top 10:2021 A04 (2026-09-15).
Internal: AXGuard /axguard-threat-model command + CSO skill.

Download now (ZIP)

  • Other versions40 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use iac-security, container-security and 8 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.
    • hardw00tSkill

      iac-security

      Infrastructure-as-Code security scanning router for Terraform, CloudFormation, Kubernetes manifests, Helm, ARM/Bicep. Orchestrates Checkov, tfsec, Terrascan, KICS, kubesec, kube-linter, Polaris, cfn-lint/cfn-nag, and OPA/Conftest. Use when auditing IaC for misconfigurations, scanning Terraform plans, validating K8s security policies, checking cloud infrastructure compliance, or authoring custom policy-as-code (Rego).

      Also in 4 projects that use this

    • vbrevikSkill

      container-security

      Scan container images, Dockerfiles, docker-compose files, and Kubernetes manifests for security misconfigurations and vulnerabilities. Uses Trivy for image/IaC scanning and Kubescape for K8s policy compliance. Falls back to regex-based Dockerfile and K8s YAML analysis when tools are unavailable. Produces STIG V-ID-tagged findings for /stig-compliance pipeline. Use when (1) reviewing Docker or K8s configuration changes, (2) scanning container images for OS-level CVEs, (3) validating K8s RBAC and NetworkPolicy configuration, (4) before deployment. Works air-gapped with pre-downloaded vulnerability database.

      Also in 4 projects that use this

    • petrkindlmannSkill

      contract-testing

      Implement consumer-driven contract testing with Pact-JS (v16). Covers consumer test writing, broker-driven provider verification, Pact Broker setup, can-i-deploy as a deployment gate, webhook-triggered verification, pending pacts, and schema-first vs consumer-first approaches (OpenAPI/Ajv, Schemathesis). Use when: "contract test," "Pact," "consumer-driven," "API contract," "provider verification," "can-i-deploy." Not for: stubbing or mocking a dependency to isolate a test — use service-virtualization; general REST/GraphQL endpoint assertions against your own API — use api-testing. Related: api-testing, service-virtualization, ci-cd-integration, test-environments.

      Also in 3 projects that use this

    • zebbernSkill

      secure-code-review

      Systematically reviews code for SQL injection, XSS, SSRF, broken access control, cryptographic failures, and other common OWASP Top 10 vulnerabilities, providing vulnerable code examples and ready-to-use remediation guidance. Trigger this skill when users ask for a security review, vulnerability scan, or penetration testing assistance, or mention keywords like OWASP, SQL injection, XSS, code audit, or security checklist.

      Also in 3 projects that use this

    • dkprogSkill

      dependency-management

      Apply when wiring dependencies, integrating external services, or designing interfaces between modules. Ensures loose coupling through dependency injection, interface segregation, and proper abstraction boundaries.

      Also in 3 projects that use this

    • OpenAISkill

      observability

      Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

      Also in 4 projects that use this

  • In this repository39 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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