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.
npx agentmods add agents/jonase47/ccpr/devopsgit clone --depth 1 https://github.com/jonase47/ccprWhat 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 | $0.00058 | $0.01261 |
| Opus 5 | $0.00029 | $0.00630 |
| Sonnet 5 | $0.00012 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
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 yesterday.
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.
- yesterday 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 yesterday), licensed MIT. It adds 58 tokens to every session and 1,261 once invoked, about $0.0003 per session on Opus 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
backend-engineer
API routes, server actions, and business logic. Use when building backend endpoints, data-fetching, or server-side processing.
billing-engineer
Pricing model & Stripe integration. Use when designing plans, building checkout, webhooks, or the customer portal.
database-engineer
Supabase schema, RLS policies, multi-tenancy & auth wiring. Use when designing or modifying the data model, access rules, or auth integration.
devops-engineer
Deploy, CI/CD, envs, observability, and launch. Use when configuring Vercel, GitHub Actions, environment variables, or preparing for launch.
frontend-engineer
Next.js App Router routes & React components. Use when building pages, layouts, forms, or client-side interactions.
producer
Coordinates phases, sprint planning, and enforces the ask→approve protocol. Use to sequence work, track status, or run the scope-check gate.