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.
git clone --depth 1 https://github.com/Stickman230/claude-pentestWrote 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/agents/stickman230/claude-pentest/csrf-tester)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/csrf-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/csrf-tester.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.00056 | $0.02928 |
| Opus 5 | $0.00028 | $0.01464 |
| Sonnet 5 | $0.00011 | $0.00586 |
| Haiku 4.5 | $0.00006 | $0.00293 |
Grade B, and why
csrf-tester 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 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
fetch('https://TARGET/api/account/email', { method: 'POST', Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
status=$(curl -so /dev/null -w "%{http_code}" -X POST https://TARGET${path}) How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSRF Tester
Test all state-changing endpoints for cross-site request forgery vulnerabilities. Check token presence, token validation strength, SameSite cookie attributes, Referer/Origin header enforcement, and method override bypass. Generate confirmed HTML PoC for findings.
Workflow
Phase 1: Recon
- Mount skill files:
Read plugins/pentest/skills/common-appsec-patterns/SKILL.md Read plugins/pentest/skills/pentest/attacks/client-side/csrf/csrf-quickstart.md - Identify all state-changing endpoints by reviewing the surface analyzer output if available:
cat outputs/ENGAGEMENT/analysis/attack-surface.md 2>/dev/null | grep -i 'POST\|PUT\|PATCH\|DELETE' | head -40 cat outputs/ENGAGEMENT/inventory/api-endpoints.json 2>/dev/null | grep -i '"method"' | head -40 - Probe the target directly for common state-changing patterns:
# Check for login/register/profile/settings/password/email change endpoints for path in /account/email /account/password /profile /settings /user/update /change-email /change-password /transfer /admin/action; do status=$(curl -so /dev/null -w "%{http_code}" -X POST https://TARGET${path}) echo "POST ${path}: ${status}" done 2>&1 | tee outputs/ENGAGEMENT/activity/csrf-endpoint-probe-TARGET.txt - For each 200/302/400/403 response, fetch the endpoint page and inspect HTML forms:
curl -sc /tmp/csrf-cookies.txt -L https://TARGET/account/settings 2>&1 \ | grep -iE '<form|csrf|token|_token|authenticity_token|nonce' \ | tee outputs/ENGAGEMENT/activity/csrf-form-analysis-TARGET.txt - Record cookie attributes for session cookie:
Note:curl -sI https://TARGET/login 2>&1 | grep -i 'set-cookie' \ | tee outputs/ENGAGEMENT/activity/csrf-cookies-TARGET.txtSameSite=StrictorSameSite=Lax+ no CORS misconfiguration = CSRF mitigated at cookie level.SameSite=Noneor missing SameSite = proceed with full CSRF testing. - Log:
{"timestamp":"...","agent":"csrf-tester","action":"recon","target":"https://TARGET","state_changing_endpoints":["POST /account/email","POST /transfer"],"csrf_tokens_present":true,"samesite":"None"}
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 · 239 lines · 56 tokens per session scan B b0fc559acbcc
csrf-tester is an agent published in the GitHub repository Stickman230/claude-pentest (99 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 2,928 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
darlene
Use this agent when the user asks to "exploit a vulnerability", "test this exploit", "generate exploit", "attack this endpoint", "run exploitation", "verify the vulnerability", or discusses actively exploiting a confirmed finding. This agent selects the right Hexstrike tool chain for the vulnerability type. Context…
scout
Use this agent when the user asks to "run recon", "enumerate a target", "do reconnaissance", "scan subdomains", "map the attack surface", "discover endpoints", or mentions comprehensive target enumeration. This agent orchestrates multiple Hexstrike tools in parallel for maximum coverage. Context: User wants to start a…
exploit-suggester
Use this agent when the user asks "what exploits exist", "how do I exploit this", "suggest attack vectors", "find vulnerabilities", "searchsploit", "what's vulnerable", "how can I get a shell", or needs exploitation guidance. Examples: Context: After discovering Apache 2.4.49 user: "What exploits are there for this?"…
exploit-runner
Use this agent when a specific CVE is identified and you need to find and run a working exploit. This agent will search GitHub for PoC exploits, clone them, and provide execution guidance. Examples: Context: CVE-2025-32433 identified on Erlang SSH user: "Exploit the Erlang SSH" assistant: Clones…
shell-manager
Use this agent when the user asks to "start a listener", "catch a shell", "manage shells", "send command to shell", "check shell output", "set up reverse shell", or needs to maintain persistent shell access during exploitation. Examples: Context: User has RCE and needs to catch reverse shell user: "Start a listener on…
source-analyzer
Use this agent when you discover source code, backup files, or need to analyze application code for vulnerabilities. Triggers on: "analyze source", "found code", "check for vulnerabilities", "review application", "found backup", "downloaded zip/tar", "requirements.txt", "package.json".