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/ersinkoc/security-check/sc-ssrfnpx skills add ersinkoc/security-check --skill sc-ssrfgit clone --depth 1 https://github.com/ersinkoc/security-checkWrote 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/ersinkoc/security-check/sc-ssrf)<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-ssrf"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-ssrf.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.00851 |
| Opus 5 | $0.00013 | $0.00426 |
| Sonnet 5 | $0.00005 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade C, and why
sc-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 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.
Cloud metadata endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- AWS: `http://169.254.169.254/latest/meta-data/` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"requests.get(", "requests.post(", "urllib.request.urlopen(", How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SC: Server-Side Request Forgery (SSRF)
Purpose
Detects SSRF vulnerabilities where user-controlled input influences server-side HTTP requests, enabling attackers to access internal services, cloud metadata endpoints, and private network resources. Covers direct SSRF, blind SSRF, DNS rebinding, and partial SSRF through header injection.
Activation
Called by sc-orchestrator during Phase 2. Runs against all web applications and APIs.
Phase 1: Discovery
Keyword Patterns to Search
"requests.get(", "requests.post(", "urllib.request.urlopen(",
"http.Get(", "http.Post(", "http.NewRequest(",
"fetch(", "axios.get(", "axios.post(", "got(",
"curl_exec(", "file_get_contents(", "fopen(",
"HttpClient", "WebClient", "HttpWebRequest",
"RestTemplate", "WebClient.create(", "OkHttpClient"
Data Flow: User Input → HTTP Request URL
# VULNERABLE
url = request.GET['url']
response = requests.get(url) # User controls entire URL
# VULNERABLE: Partial SSRF
host = request.GET['host']
response = requests.get(f"https://{host}/api/data") # User controls host
# SAFE: URL allowlist
ALLOWED_HOSTS = ['api.example.com', 'cdn.example.com']
parsed = urlparse(request.GET['url'])
if parsed.hostname not in ALLOWED_HOSTS:
return HttpResponseForbidden()
response = requests.get(request.GET['url'])
Cloud Metadata Endpoints
Flag any request that could reach:
- AWS:
http://169.254.169.254/latest/meta-data/ - GCP:
http://metadata.google.internal/ - Azure:
http://169.254.169.254/metadata/instance
IP Bypass Techniques to Check
When blocklists are used, verify they catch:
- Decimal:
2130706433(127.0.0.1) - Hex:
0x7f000001 - Octal:
0177.0.0.1 - IPv6:
[::1],[::ffff:127.0.0.1] - DNS rebinding: attacker domain resolving to internal IP
Severity Classification
- Critical: SSRF accessing cloud metadata or internal admin services
- High: SSRF to arbitrary internal hosts, blind SSRF with out-of-band confirmation
- Medium: SSRF with limited impact (port scanning), partial URL control
- Low: SSRF with strong allowlist that may have minor bypass
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 · 92 lines · 26 tokens per session scan C 748a28de333e
sc-ssrf is a skill published in the GitHub repository ersinkoc/security-check (56 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 851 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…