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 skills add ByamB4/find-cve-agent --skill ssrfgit clone --depth 1 https://github.com/ByamB4/find-cve-agentWrote 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/byamb4/find-cve-agent/ssrf)<a href="https://agentmods.dev/skills/byamb4/find-cve-agent/ssrf"><img src="https://agentmods.dev/badge/skills/byamb4/find-cve-agent/ssrf/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.
<a href="https://agentmods.dev/skills/byamb4/find-cve-agent/ssrf"><img src="https://agentmods.dev/badge/skills/byamb4/find-cve-agent/ssrf.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00978 |
| Opus 5 | $0.00014 | $0.00489 |
| Sonnet 5 | $0.00006 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade C, and why
ssrf scanned grade C 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 9d 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 endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- AWS IMDSv1: `http://169.254.169.254/latest/meta-data/iam/security-credentials/` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
grep -rn "urllib\|url\.parse\|new URL(" . How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSRF Detection
When to Use
Audit webhook handlers, URL preview generators, import-from-URL features, image proxy endpoints, PDF generators that fetch remote resources, and any endpoint that makes HTTP requests based on user-supplied URLs.
Process
Step 1: Find HTTP Request Sinks
# JavaScript
grep -rn "fetch(\|axios\|got(\|node-fetch\|http\.get\|https\.get\|request(" .
grep -rn "urllib\|url\.parse\|new URL(" .
# Python
grep -rn "requests\.get\|requests\.post\|urllib\.request\|urlopen\|httpx" .
# Go
grep -rn "http\.Get\|http\.Post\|http\.NewRequest\|httpClient" .
# Ruby
grep -rn "Net::HTTP\|open-uri\|Faraday\|HTTParty\|RestClient" .
Step 2: Check If URL is User-Controlled
Trace the URL parameter backwards:
- Does it come from request parameters, body, headers?
- Is it stored in database but originally user-supplied?
- Can the user control the host/port/path/scheme?
Step 3: Check URL Validation
grep -rn "isPrivate\|isInternal\|isLocalhost\|blocked\|allowlist\|blocklist" .
grep -rn "127\.0\.0\.1\|0\.0\.0\.0\|169\.254\|10\.\|172\.16\|192\.168" .
Step 4: Test IP Validation Bypasses
Common bypass techniques:
- Decimal IP:
2130706433= 127.0.0.1 - Hex IP:
0x7f000001= 127.0.0.1 - Octal IP:
0177.0.0.1= 127.0.0.1 - IPv6 mapped:
::ffff:127.0.0.1 - IPv6 localhost:
::1,0:0:0:0:0:0:0:1 - URL encoding:
http://127%2e0%2e0%2e1 - DNS rebinding: domain that resolves to 127.0.0.1 after initial check
- Redirect following: allowed URL redirects to internal URL
0.0.0.0on some systems maps to localhostlocaltest.meresolves to 127.0.0.1
Step 5: Check Protocol Handling
Dangerous protocols beyond http/https:
file:///etc/passwd-- local file readgopher://-- arbitrary TCP data (SSRF amplifier)dict://-- dictionary service probeftp://-- FTP data exfiltration
Step 6: Evaluate Cloud Metadata Access
If the target runs on cloud infrastructure:
- AWS IMDSv1:
http://169.254.169.254/latest/meta-data/iam/security-credentials/ - AWS IMDSv2: requires token header (harder to exploit)
- GCP:
http://metadata.google.internal/computeMetadata/v1/ - Azure:
http://169.254.169.254/metadata/instance - DigitalOcean:
http://169.254.169.254/metadata/v1/
What ships with it
3 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.
- 9d ago First seen · 100 lines · 28 tokens per session scan C 3a66939afb83
ssrf is a skill published in the GitHub repository ByamB4/find-cve-agent (48 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 978 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C 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
wordpress-plugin-hunt
Hunt WP plugins via REST, exploit CVEs when version known.
deep-invade
Deep pentest WP: SSRF, plugin CVE, JS mine, port scan chain.
zimbra-attack
Zimbra SOAP user enum, CVE-2022-37042, SSRF when webmail.
wp-plugin-cve-hunt
Systematic approach to finding and testing CVEs for identified WordPress plugins. Covers plugin discovery, version extraction from multiple sources (readme.txt, assets, inline JS), CVE database cross-referencing with WPScan/Patchstack/NVD/NVD API, version-based vulnerability matching, exploitation PoC generation, and…
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
bug-bounty-hunting
Hunt vulnerabilities like an expert, not a linear software engineer: come at a target from the overlooked angle, reason by analogy and transfer proven attack mechanisms, attack the hidden assumptions and the seams between systems, drill to the mechanism, then keep it honest with proof and persistence (acceptance !=…