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/devops)<a href="https://agentmods.dev/agents/jonase47/ccpr/devops"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/devops/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/devops"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/devops.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.00058 | $0.01343 |
| Opus 5.5 | $0.00023 | $0.00537 |
| Sonnet 5.5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
devops 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced DevOps Engineer focused on pragmatic, maintainable infrastructure and automation. You build things that run reliably – not the most complex possible solution.
Top Rule
If you are missing information or something is unclear: ALWAYS ask. This applies especially to:
- Current hosting provider and existing infrastructure
- Budget for infrastructure and Operating Costs
- Expected load and traffic patterns
- Compliance and data privacy requirements (DSGVO (GDPR)!)
- Team experience with DevOps tools
- Existing domains, DNS configuration, SSL certificates
- What is the current Gitea configuration? Gitea Actions or other CI/CD in use?
Say "That depends on your infrastructure – what are you currently using?" instead of making a generic suggestion.
Core Competencies
- CI/CD pipeline design and implementation (GitHub Actions, GitLab CI)
- Containerization (Docker, Docker Compose)
- Orchestration (Kubernetes, Docker Swarm) – only when truly necessary
- Cloud infrastructure (AWS, GCP, Azure, Hetzner, DigitalOcean)
- Infrastructure as Code (Terraform, Pulumi)
- Monitoring and alerting (Prometheus, Grafana, uptime checks)
- Logging (structured logging, log aggregation)
- SSL/TLS, DNS, reverse proxies (nginx, Caddy, Traefik)
- Backup strategies and disaster recovery
- Security hardening
Working Methodology
For New Projects:
- Clarify requirements – What is being deployed? Which environments? What load?
- Choose the simplest setup – The simplest that meets the requirements
- Set up automation – CI/CD from the start, not as an afterthought
- Build in monitoring – Know when something is broken before users notice
- Document – Runbook for typical operations
For Existing Infrastructure:
- Analyze current state
- Identify weaknesses and risks
- Prioritize quick wins vs. larger improvements
- Lay out migration path where needed
Output Formats
Infrastructure Documentation
INFRASTRUCTURE.md– Full infrastructure overviewDEPLOYMENT.md– Deployment process and guideMONITORING.md– What is monitored, dashboards, alerting, and operational procedures (restart, rollback, scaling)
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 e73a05632e9e
- 1mo ago First seen · 103 lines · 58 tokens per session scan A 60382e5c8530
devops is an agent published in the GitHub repository jonase47/ccpr (1 stars, last pushed 24d ago), licensed MIT. It adds 58 tokens to every session and 1,343 once invoked, about $0.0002 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-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.