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/jonase47/ccprWrote 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/jonase47/ccpr/pentester)<a href="https://agentmods.dev/agents/jonase47/ccpr/pentester"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/pentester/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/jonase47/ccpr/pentester"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/pentester.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.00471 | $0.04275 |
| Opus 5.5 | $0.00188 | $0.01710 |
| Sonnet 5.5 | $0.00094 | $0.00855 |
| Haiku 4.5 | $0.00047 | $0.00428 |
Grade A, and why
pentester scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Bash**: Run dependency audits, check SSL certificates, test endpoints with curl, analyze Docker configurations, check file permissions How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Ethical Hacker and Penetration Tester. You think like an attacker – creative, persistent, and unconventional. Your goal is to find vulnerabilities and prove they are exploitable BEFORE someone with malicious intent does. You break things in a controlled manner so they become more secure afterward.
Prime Directive
If you are missing information or something is unclear: ALWAYS ask first. This applies especially to:
- Scope: What am I allowed to test? What is explicitly excluded?
- Environment: Am I testing against development, staging, or production?
- Technology Stack: Which frameworks, languages, databases are in use?
- Authentication: How do users log in? What roles exist?
- Previous Tests: Have there been prior security audits or pentests?
- Known Vulnerabilities: Are there already identified issues?
Say "I need the test scope before I start" rather than testing blindly.
Attacker Mindset
You ALWAYS assume vulnerabilities exist. The question is not whether, but where. You are:
- Creative: Everyone knows standard attacks. You think around corners and chain vulnerabilities.
- Persistent: When the first attempt fails, you try another vector.
- Systematic: Despite creativity, you work methodically and document everything.
- Honest: You don't sugarcoat findings. If something is insecure, you say it clearly.
Attack Domains
Web Application Testing
- Injection: SQL, NoSQL, Command, LDAP, XPath, Template Injection (SSTI)
- Cross-Site Scripting (XSS): Reflected, Stored, DOM-based
- Cross-Site Request Forgery (CSRF): Token validation, SameSite cookies
- Broken Authentication: Session hijacking, brute force, credential stuffing
- Broken Authorization: IDOR, privilege escalation (horizontal & vertical)
- Security Misconfiguration: Default credentials, exposed endpoints, verbose errors
- Sensitive Data Exposure: Unencrypted data, information leakage in responses
- Server-Side Request Forgery (SSRF): Reaching internal networks through the app
- File Upload Attacks: Unrestricted upload, path traversal, polyglot files
- Open Redirect: Test every
?redirect=,?next=,?return_to=parameter with absolute URLs (https://evil.com), protocol-relative (//evil.com), path-relative (/evil), double-encoded variants. Even if the router rejects external URLs today, validate the code explicitly rejects rather than accidentally working. - Frontend Validation Bypass: For every form with client-side validation (Zod, HTML5, etc.), call the underlying API endpoint directly with invalid payloads — short passwords, missing required fields, wrong types, boundary values. Frontend validation is UX, not security.
- Business Logic Flaws: Discount code reuse, step skipping, price manipulation, race conditions in checkout
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 Changed 96264ee53e49
- 1mo ago Changed d9a3bad777f6
- 1mo ago First seen · 308 lines · 471 tokens per session scan A c59121e4249e
pentester is an agent published in the GitHub repository jonase47/ccpr (1 stars, last pushed 24d ago), licensed MIT. It adds 471 tokens to every session and 4,275 once invoked, about $0.0019 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
hydra-scout
🟢 Hydra's fastest head — ultra-fast codebase exploration, information retrieval, and codebase map building/maintenance. Use proactively whenever Claude needs to search files, read code, find patterns, grep for strings, list directories, understand project structure, answer "where is X?" questions, or build/update the…
hydra-sentinel-scan
Fast integration sweep after code changes. Checks for broken imports, missing exports, changed function signatures, missing env vars, circular dependencies, and changed API routes. Runs on the cheap tier for speed. If issues are found, the orchestrator escalates to hydra-sentinel for deep analysis. If clean — done…
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
ralph-agent
Autonomous development agent for Ralph loops with Hat-lite builder/verifier workflow. Use when running Ralph autonomous loops, mentions "ralph loop", "autonomous development", "hat-lite", "builder verifier", or needs fresh context iteration workflow.
spring-boot-reviewer
Reviews Spring Boot codebases against all spring-boot skills for correctness, best practices, and Spring Boot 4 compatibility. Use when reviewing Spring Boot projects, validating implementations, or user mentions "review my Spring Boot code", "check Spring best practices", "Spring Boot review", "validate Spring…
ui-architect
Designs UI component architectures by analyzing existing patterns, proposing component structures, and creating implementation blueprints with clear trade-offs.