capec

capec is a skill for Claude Code from 0dayInc/pwn. It costs 14 tokens per session (687 once invoked), scanned A, original, MIT.

A security-testing skill based on CAPEC, a catalogue of documented ways attackers can exploit software. It follows relevant attack patterns and links them to CWE weakness descriptions.

In plain words
What is it for?
Use it when testing a named CAPEC attack pattern, an ATT&CK technique, or all applicable attack patterns for a system.
Why use it?
It gives security reviews a structured list of attack steps instead of relying only on general checks.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Install

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.

agentmods
npx agentmods add skills/0dayinc/pwn/capec
Any agent
npx skills add 0dayInc/pwn --skill capec
Clone the repo
git clone --depth 1 https://github.com/0dayInc/pwn

Made for: Claude Code.

Wrote 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.

agentmods badge for capec

README.md
[![agentmods](https://agentmods.dev/badge/skills/0dayinc/pwn/capec.svg)](https://agentmods.dev/skills/0dayinc/pwn/capec)
Your own site
<a href="https://agentmods.dev/skills/0dayinc/pwn/capec"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/capec.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 687 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00687
Opus 5 $0.00007 $0.00344
Sonnet 5 $0.00003 $0.00137
Haiku 4.5 $0.00001 $0.00069

Measured 6d ago against content hash cc98bf3437bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

capec 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 6d 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.

etc/default_skills/capec/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CAPEC exhaustive testing

Use when the ask names a CAPEC ID, an ATT&CK technique that maps to CAPEC, or "execute this attack pattern". Pair with the cwe skill: CAPEC is how the attack is performed; CWE is the weakness you prove.

When to use

  • "CAPEC-66", "attack pattern", "how would an attacker XSS this"
  • Purple-team / red-team playbooks that need a numbered flow
  • Coverage pass: every CAPEC that applies to this stack

Methodologies

Catalog Role
CAPEC List 3.9 attack pattern IDs, views, categories
CWE (bundled cwe skill) weakness IDs related to each pattern
ATT&CK adversary technique mapping when present
OWASP WSTG web execution of HTTP-related patterns

How to look up a CAPEC

Each CAPEC number is a file in this skill:

references/CAPEC-<id>.md

Examples: references/CAPEC-66.md, references/CAPEC-1.md. Open that file and follow its procedure end-to-end, including every related CWE via ../cwe/references/CWE-<id>.md. references/INDEX.md lists every ID.

Exhaustive catalog procedure

  1. Identify the target class (web, API, native, firmware, human, network).
  2. Pick a CAPEC view (CAPEC-1000 Mechanisms of Attack, etc.).
  3. For every applicable member, run references/CAPEC-<id>.md.
  4. Record N/A with a reason when prerequisites cannot be met.
  5. Findings cite the member CAPEC and related CWE IDs.
  6. Re-read saved evidence before calling the pattern tested.

Tooling

  • Always: skills_recall this skill, then read the CAPEC reference.
  • Then: skills_recall cwe for related weakness procedures.
  • HTTP: PWN::Plugins::BurpSuite or TransparentBrowser.
  • Source: PWN::SAST::Factory.start / pwn_sast.
  • Authz: PWN::Bounty::LifecycleAuthzReplay.

Pitfalls

  • Categories and views are groupings; they are not attacks.
  • Skipping the related CWE procedure leaves the weakness unproven.
  • One blocked payload is not an exhaustive CAPEC test.
  • Do not skip deprecated IDs without following the replacement.

Read the full file on GitHub · 84 lines

Files

What ships with it

60 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.

Changes

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.

  1. 6d ago First seen · 84 lines · 14 tokens per session scan A cc98bf3437bf

Subscribe to this mod's changes

capec is a skill published in the GitHub repository 0dayInc/pwn (78 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 687 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

analyzing-linux-elf-malware

Analyze malicious Linux ELF binaries — botnets, cryptominers, ransomware, and rootkits targeting Linux servers, containers, and cloud infrastructure — through static analysis, dynamic tracing, and reverse engineering of x8664 and ARM samples. Use when investigating Linux malware, triaging a suspicious ELF binary…

mukul975/Anthropic-Cybersecurity-Skills · 82 tokens

osmedeus-expert

Expert guide for the Osmedeus security automation workflow engine. Use when: (1) writing or editing YAML workflows (modules and flows), (2) running osmedeus CLI commands (scan, workflow management, installation, server), (3) configuring steps, runners, triggers, or template variables, (4) debugging workflow execution…

j3ssie/osmedeus · 113 tokens

supabase

Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…

PentesterFlow/agent · 120 tokens

graphql

GraphQL pentest playbook — find the endpoint, dump the schema (introspection or field-suggestion fallback), then test for authorization gaps, query batching, alias overload, depth-based DoS, and SQLi/NoSQLi in resolver arguments. Use when the target exposes a /graphql endpoint, GraphiQL, Apollo, or accepts GraphQL…

PentesterFlow/agent · 75 tokens

jwt

JWT attack playbook — algorithm confusion (alg=none, HS/RS confusion), kid path traversal/SQLi, jku/x5u SSRF, weak HS256 cracking, and embedded JWK trickery. Use when the target uses JWTs for auth (header.payload.signature).

PentesterFlow/agent · 60 tokens

recon

External recon playbook for a web target — subdomain enumeration, live-host probing, tech fingerprinting, and a first pass at content discovery. Use when the user gives you a root domain or apex and wants attack surface mapping.

PentesterFlow/agent · 49 tokens