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.
npx agentmods add skills/0dayinc/pwn/penetration-testingnpx skills add 0dayInc/pwn --skill penetration-testinggit clone --depth 1 https://github.com/0dayInc/pwnWrote 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.
[](https://agentmods.dev/skills/0dayinc/pwn/penetration-testing)<a href="https://agentmods.dev/skills/0dayinc/pwn/penetration-testing"><img src="https://agentmods.dev/badge/skills/0dayinc/pwn/penetration-testing.svg" alt="Measured on agentmods" height="20"></a>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.00026 | $0.00819 |
| Opus 5 | $0.00013 | $0.00409 |
| Sonnet 5 | $0.00005 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
penetration-testing 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Penetration Testing
Use when the ask is an engagement-style test of hosts, apps, or a lab
network: recon, exploit, limited post-ex, report. One nmap listing is
not a pentest.
When to use
- "pentest this lab / CIDR / app"
- chain discovery -> vuln -> proof -> notes
- internal-style test with PWN plugins
Methodologies
Follow PTES end-to-end. Overlay the catalog that matches the surface:
| Catalog | When |
|---|---|
| PTES | default 7 phases: pre-engage, intel, threat model, vuln analysis, exploit, post-ex, report |
| NIST SP 800-115 | federal / structured technical assessment language |
| OSSTMM | channels: human, physical, wireless, telecom, data |
| ISSAF | detailed control-by-control assessment |
| OWASP WSTG | web / API portion (or switch to web-application-penetration-testing) |
| MITRE ATT&CK | label post-ex and lateral movement |
| PCI DSS pentest guidance | cardholder-data environments |
Tooling
- Discover:
PWN::Plugins::NmapIt,PWN::Plugins::Packet,PWN::Plugins::IPInfo,PWN::Plugins::Shodan. - Web: Burp preferred, ZAP fallback,
TransparentBrowservia the proxy. - Creds / dirs:
PWN::Plugins::Fuzz,OpenAPI,Spider. - Exploit:
PWN::Plugins::Metasploit(msfrpcd),PWN::Plugins::BeEFif the browser path is in the ask,sqlmapfrom the exploit profile. - Wireless / RF only if the ask is RF:
PWN::SDR,pwn_gqrx_scanner. - Report:
PWN::Reports::*.
nmap = PWN::Plugins::NmapIt.port_scan(target: '10.0.0.0/24')
msf = PWN::Plugins::Metasploit.connect
PWN::Plugins::Metasploit.search(msf_obj: msf, query: 'http')
Procedure
- Write the engagement note: targets, exclusions, start time. Then work.
- Host discovery + port/service scan. Save XML/JSON, read it back.
- Fingerprint and prioritize (exposed admin, old stacks, default creds).
- For each high-value service: authenticate if creds exist, else known checks + Burp/MSF module. Prove impact with a reversible action (id, file read, new low-priv session).
- Post-ex only as far as the ask (one hop, no ransomware-shaped noise).
- Report: hosts, findings, evidence paths, severity, fix. Close browser and MSF sessions you opened.
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.
- 6d ago First seen · 82 lines · 26 tokens per session scan A a2fd15148184
penetration-testing is a skill published in the GitHub repository 0dayInc/pwn (78 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 819 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.
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…
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…
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…
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…
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).
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.