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/pentesterflow/agent/webvulnnpx skills add PentesterFlow/agent --skill webvulngit clone --depth 1 https://github.com/PentesterFlow/agentWhat 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.00053 | $0.01189 |
| Opus 5 | $0.00026 | $0.00594 |
| Sonnet 5 | $0.00011 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade B, and why
webvuln scanned grade B with 2 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 2d 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
Any parameter that takes a URL or hostname: try `http://127.0.0.1`, `http://169.254.169.254/latest/meta-data/`, and an out-of-band canary the user provides. Compare response timings and bodies with curl `-w "%{time_total Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Default to curl and the built-in `http` tool. Do not pull in heavy scanners (nuclei, sqlmap, ffuf, etc.) unless the user explicitly asks for them or you have manually confirmed a bug and need a scanner only to characteri 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.
Web vuln hunting playbook
You are testing specific endpoints the user has handed you (or that came out of the recon skill). Every finding must come with a real PoC and a concrete impact statement — no theoretical bugs.
Default to curl and the built-in http tool. Do not pull in heavy scanners (nuclei, sqlmap, ffuf, etc.) unless the user explicitly asks for them or you have manually confirmed a bug and need a scanner only to characterize the bug class.
Execution rule: substitute real target values before running commands. Never write literal placeholders such as <TARGET>, <vulnerable-path>, or <PoC body> to files. If a value is unknown, ask once or derive it from /target.
1. Triage the target
Fetch the landing page with the http tool or curl. Note:
- Framework / language signals (cookies, headers, error pages)
- Authentication scheme (cookie, Bearer, basic)
- API style (REST / GraphQL / gRPC)
- Anything that suggests a known CVE family (versioned banner, vendor product name)
If you spot a versioned product, immediately web_search "<product> <version> CVE" and web_fetch the top advisory. Reproduce the CVE manually with curl before reporting.
2. Known-CVE pass (manual, curl-driven)
For each suspected CVE pulled from the advisory, craft the curl that proves it — single request when possible:
TARGET="https://app.example.com" # replace with the scoped target before running
curl -ksS -X POST "$TARGET/vulnerable-path" \
-H 'Content-Type: application/json' \
-d '{"replace":"with-real-poc-body"}' \
-w "\nHTTP %{http_code} size=%{size_download} time=%{time_total}\n"
If the advisory describes a recognizable pattern (template injection, deserialization, etc.) and the user has explicitly authorized broader scanning, then — and only then — reach for nuclei against the single host. Otherwise stay manual.
3. Auth + access control (IDOR / BAC)
- Identify any numeric or UUID identifiers in the URL path or query (
/api/users/12345,/orders/?id=...). - With user-provided session A, fetch a resource you own.
- Swap the identifier to another user's value (or use a second session from the user) and replay with curl or the
httptool. - A 200 with foreign data = IDOR. Capture the curl one-liner and the response excerpt into
findings/idor-<endpoint>.txt.
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.
- 2d ago First seen · 88 lines · 53 tokens per session scan B 1df7b5f1a110
webvuln is a skill published in the GitHub repository PentesterFlow/agent (1,316 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,189 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
osint
Drive extroosint with the right kind, feeds, pivots, and keys.
cwe
Exhaustively test a target against every applicable CWE.
penetration-testing
Run a scoped pentest with NmapIt, Burp, Metasploit, and a written report.
pwn-ai-agent-curriculum
Drive PWN::AI::Agent::Curriculum from pwneval.
pwn-ai-agent-loop
Drive PWN::AI::Agent::Loop from pwneval.
pwn-ai-agent-reward
Drive PWN::AI::Agent::Reward from pwneval.