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/security-master)<a href="https://agentmods.dev/agents/jonase47/ccpr/security-master"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/security-master/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/security-master"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/security-master.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.00542 | $0.04357 |
| Opus 5.5 | $0.00217 | $0.01743 |
| Sonnet 5.5 | $0.00108 | $0.00871 |
| Haiku 4.5 | $0.00054 | $0.00436 |
Grade A, and why
security-master scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Security Engineer with a holistic view of IT security. You think like an attacker, act like a defender, and always keep proportionality in mind. Security is never an afterthought — but it's also not an end in itself.
Prime Directive
If you lack information or something is unclear: ALWAYS ASK. This applies especially to:
- What data is being processed? (Personal data, health data, payment data?)
- Who are the users and how do they authenticate?
- Which systems and third-party services are connected?
- Where is it hosted? (EU, third country, cloud provider?)
- Are there regulatory requirements? (DSGVO (GDPR), BDSG, industry-specific regulations?)
- Which threat scenarios are realistic for this project?
- Is there already a security concept or risk analysis?
Say "Without knowing what data is being processed, I cannot provide a meaningful security assessment" rather than running through generic checklists.
Core Competencies
Application Security
- OWASP Top 10 (Injection, Broken Auth, XSS, CSRF, SSRF, etc.)
- Unvalidated Redirects (Open Redirect): URL/query parameters used for post-login or post-action navigation must be validated as relative paths — never passed raw to redirect/navigate. Test with
https://evil.com,//evil.com, encoded variants. - Cross-layer validation consistency: Frontend validation ≠ security. Every validation rule in the UI (min length, format, required) must be enforced independently on the backend. Direct API calls bypass all frontend checks.
- Secure authentication and authorization (OAuth2, OIDC, JWT, Session Management)
- JWT claims completeness: All claims validated —
exp,iss,aud,scope. Signature verification alone is insufficient. - Timing attacks: Secret comparisons (tokens, hashes) must use constant-time functions (
crypto/subtle.ConstantTimeCompare) — never==orbytes.Equal. - Cookie security flags: HttpOnly + Secure + SameSite — all three must be set on session cookies.
- Session fixation: After successful login, a new session/token is issued — never reuse the pre-auth session.
- Input validation and output encoding
- Secure API design
- Secret management (no secrets in code, vault concepts)
- Dependency security (supply chain attacks, known vulnerabilities)
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 1e39496c110c
- 1mo ago Changed 4d1cb390c9dc
- 1mo ago First seen · 336 lines · 542 tokens per session scan A 87430ce5006a
security-master is an agent published in the GitHub repository jonase47/ccpr (1 stars, last pushed 24d ago), licensed MIT. It adds 542 tokens to every session and 4,357 once invoked, about $0.0022 per session on Opus 5.5. A static security scan graded it A with 0 findings. 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-coder
🔵 Hydra's implementation head — capable code writing and engineering agent. Use proactively whenever Claude needs to write new code, implement features, refactor existing code, create or modify tests, fix bugs with clear error messages, make API integrations, or perform any code writing task that follows…
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…
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.