A security-testing workflow that checks a target against every relevant CWE. CWE, or Common Weakness Enumeration, is a catalogue of recurring software security flaws.

It is for testing applications, source code, binaries, or firmware against named weaknesses, CVE-related flaws, or all applicable weaknesses for a technology stack.

It provides a structured way to investigate known weakness types instead of relying on an incomplete spot check.

cwe — Skill for Claude Code by 0dayInc/pwn

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.

Any agent

npx skills add 0dayInc/pwn --skill cwe

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/0dayinc/pwn/cwe/github.svg)](https://agentmods.dev/skills/0dayinc/pwn/cwe)

Your own site

<a href="https://agentmods.dev/skills/0dayinc/pwn/cwe"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/cwe/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/0dayinc/pwn/cwe"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/cwe.svg" alt="Reviewed on agentmods" width="80" 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 761 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high YARA Match · line 62
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).

Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.00761
Opus 5.5	$0.00006	$0.00304
Sonnet 5.5	$0.00003	$0.00152
Haiku 4.5	$0.00001	$0.00076

Measured 1mo ago against content hash 4f6c94c95049, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cwe 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 1mo 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/cwe/SKILL.md · 88 lines

How it starts

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

CWE exhaustive testing

Use when the ask names a CWE, OWASP/WSTG mapping to CWE, a CVE that maps to CWE, SAST output with CWE IDs, or "test this app/binary/firmware against CWE". Pair with sast-code-scans when source exists and web-application-penetration-testing when the surface is HTTP.

When to use

"CWE-79", "test for SQLi", "map findings to CWE"
CVE analysis that must name the underlying weakness
Coverage pass: every CWE that applies to this stack

Methodologies

Catalog	Role
CWE List 4.20	weakness IDs, views, categories — source of each reference
OWASP WSTG / ASVS	web mapping onto CWE IDs
NIST SP 800-115	technical assessment techniques wrapping these tests
ATT&CK / CAPEC	attacker technique; still report the CWE

How to look up a CWE

Each CWE number is a file in this skill:

references/CWE-<id>.md

Examples: references/CWE-79.md, references/CWE-89.md, references/CWE-787.md. Open that file and follow its procedure end-to-end. Do not improvise a one-line "XSS test" when the reference exists. references/INDEX.md lists every ID.

Exhaustive catalog procedure

Identify the target class (web, API, native, firmware, cloud, human).
Pick a CWE view (CWE-1000 Research Concepts, CWE-699 Software Development, CWE-1194 Hardware Design, CWE-1326 CWE Top 25, etc.) from references/.
For every applicable member, run references/CWE-<id>.md.
Record N/A with a reason when the platform does not exist.
Findings cite the member CWE, not only the view/category.
Re-read saved evidence before calling the CWE tested.

Tooling

Always: skills_recall this skill, then read the CWE reference file.
HTTP: PWN::Plugins::BurpSuite or TransparentBrowser.
Source: PWN::SAST::Factory.start / pwn_sast.
Authz: PWN::Bounty::LifecycleAuthzReplay.
Native: PWN::Plugins::Assembly, gdb via shell.
Hardware: PWN::Plugins::Serial, BusPirate.

Pitfalls

Scanner output is inventory, not a test.
Categories and views are groupings; they are not vulnerabilities.
One payload on one parameter is not exhaustive for a Base CWE.
Do not skip deprecated IDs without following the replacement.

Read the full file on GitHub · 88 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.

1mo ago First seen · 88 lines · 14 tokens per session scan A 4f6c94c95049

Subscribe to this mod's changes

cwe is a skill published in the GitHub repository 0dayInc/pwn (86 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 761 once invoked, about $0.0001 per session on Opus 5.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.

Security Testing bugbounty fuzzing penetration-testing reconnaissance reverse-engineering web-security

race

Race condition / TOCTOU playbook — limit overrun (one-time codes used twice, gift cards spent twice), single-packet attack (last-byte sync) to force parallel processing, and state-confusion races (file upload + read, order before payment). Use when timing-sensitive logic could be abused — one-time codes, coupons/gift…

PentesterFlow/agent · 82 tokens

exploiting-insecure-deserialization

Identifying and exploiting insecure deserialization vulnerabilities in Java, PHP, Python, and .NET applications to achieve remote code execution during authorized penetration tests.

balsm-health/Balsm-AI · 37 tokens

testing-for-business-logic-vulnerabilities

Identifying flaws in application business logic that allow price manipulation, workflow bypass, and privilege escalation beyond what technical vulnerability scanners can detect.

Njones17/AI-agent-master-cyber-skills-list · 35 tokens

testing-for-sensitive-data-exposure

Identifying sensitive data exposure vulnerabilities including API key leakage, PII in responses, insecure storage, and unprotected data transmission during security assessments.

Njones17/AI-agent-master-cyber-skills-list · 35 tokens

owasp-top-10-testing

Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…

usestrix/strix · 151 tokens

application-security-testing

Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the…

usestrix/strix · 125 tokens

cwe

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

CWE exhaustive testing

When to use

Methodologies

How to look up a CWE

Exhaustive catalog procedure

Tooling

Pitfalls

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

race

exploiting-insecure-deserialization

testing-for-business-logic-vulnerabilities

testing-for-sensitive-data-exposure

owasp-top-10-testing

application-security-testing