PentestingEverything is a structured knowledge base for penetration testing and application security across areas such as web, mobile, API, network, wireless, and source-code testing. Security testers, bug hunters, and penetration testers use it to research methods, tools, and reference material for engagements. Its catalogue skill makes this guidance available to coding agents for security testing and secure development.
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/m14r41/pentestingeverything/pentesting-everythingnpx skills add m14r41/PentestingEverything --skill pentesting-everythinggit clone --depth 1 https://github.com/m14r41/PentestingEverythingWrote 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/m14r41/pentestingeverything/pentesting-everything)<a href="https://agentmods.dev/skills/m14r41/pentestingeverything/pentesting-everything"><img src="https://agentmods.dev/badge/skills/m14r41/pentestingeverything/pentesting-everything.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 | $0.00056 | $0.01920 |
| Opus 5 | $0.00028 | $0.00960 |
| Sonnet 5 | $0.00011 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
pentesting-everything 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 5d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PentestingEverything
Use this repository as a practical, citable workflow for authorized security assessments. Prefer repository evidence over memory. Do not invent authorization, scope, or findings.
Companion sites:
- Knowledge base: https://pentesting.m14r41.in
- Checklist companion: https://checklist.m14r41.in
- Upstream repo: https://github.com/m14r41/PentestingEverything
Ground rules
- Lawful use only. Proceed only for systems the user is authorized to test.
- Never invent authorization. If scope, rules of engagement, or written permission is unclear, ask before any active testing guidance.
- Confirm before active testing. After drafting a plan or checklist, ask the user to confirm targets and constraints before recommending live attacks.
- Gate high-impact actions. Require explicit written scope for destructive tests, denial-of-service or load abuse, credential stuffing at scale, phishing or social engineering against real people, persistence, lateral movement outside agreed hosts, or exfiltration of real personal data.
- Source-grounded answers. Read repository Markdown (or the live site page) before teaching methodology, payloads, or tool commands. Cite paths and URLs used.
- Neutral, professional tone. Accurate and practical; no hype or emoji in deliverables.
- Pace automated requests. When running as an autonomous agent rather than alongside an interactive tester, respect the program's stated rate limits and testing window before looping requests. Unattended request floods are how agentic runs trigger a WAF ban or breach program rules that a human tester would have paced instinctively.
When to use
Apply when the user asks to:
- Plan or run a pentest, VAPT, or security assessment
- Build a checklist for web, API, mobile, cloud, Active Directory, network, and related domains
- Look up how to test a vulnerability class (SQL injection, IDOR, SSRF, and similar)
- Draft findings, evidence notes, or report sections from this knowledge base
- Orient inside PentestingEverything folders or the live docs site
What ships with it
2 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.
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.
- 5d ago First seen · 200 lines · 56 tokens per session scan A 48cb2d451684
pentesting-everything is a skill published in the GitHub repository m14r41/PentestingEverything (2,064 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,920 once invoked, about $0.0003 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
hunt-ato
Hunt account takeover taxonomy — 9 distinct paths to ATO, plus chains. Paths: (1) password reset flaws (host-header injection redirects token, predictable/numeric token, Referer leak, no-expiry/reuse), (2) email change without re-auth, (3) OAuth account-link CSRF, (4) MFA bypass (per hunt-mfa-bypass), (5) session…
cybersecurity
Ultimate AI-powered cybersecurity code review skill. Performs comprehensive security audit across 8 dimensions: vulnerability detection (OWASP Top 10:2021, CWE Top 25:2024), secret scanning, dependency/supply chain analysis, IaC security, threat intelligence (malware/backdoor/C2 detection, MITRE ATT&CK mapping)…
evidence-hygiene
Evidence-capture and PoC-redaction discipline for bug-bounty submissions: cookie redaction protocol (which fields to mask, Preview annotation / Burp panel hiding / DevTools workflow), PII black-bar discipline (what to mask in other-user data — names, emails, phones, faces — vs what is safe to leave — usernames, trace…
hunt-api-misconfig
Hunt API security misconfiguration — mass assignment, prototype pollution, HTTP verb tampering. Mass assignment: send {isadmin:true, role:admin, verified:true} on profile/account/reset endpoints — server blindly applies. JWT signature/crypto forging (alg:none, key confusion, kid/jku) is owned by hunt-jwt-crypto; this…
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…
apk-redteam-pipeline
End-to-end Android APK red-team pipeline — automated APK acquisition (Play Store + apkpure + apkmirror fallback), jadx decompilation, secret/URL/JWT/Firebase grep, pinned-cert extraction, exported-component enumeration, Frida runtime instrumentation templates, intent-injection probes. Built from an authorized external…