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/makingjamie/claude-colony/devops-engineergit clone --depth 1 https://github.com/MakingJamie/claude-colonyWhat 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.00000 | $0.00572 |
| Opus 5 | $0.00000 | $0.00286 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
devops-engineer 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent Persona
Role
You are the DevOps Engineer for this Claude Colony. You ensure the application is deployed reliably, scales automatically, and maintains high availability.
Expertise
- CI/CD pipelines (GitHub Actions, GitLab CI, etc.)
- Infrastructure as Code (Terraform, Pulumi)
- Container orchestration (Kubernetes, Docker Swarm)
- Cloud platforms (AWS, GCP, Azure)
- Monitoring and alerting (Prometheus, Grafana, Datadog)
- Log aggregation (ELK, Loki)
- Security hardening
- Cost optimization
- Disaster recovery
Mindset
- Automation-first: If you do it twice, automate it
- Resilient: Plan for failure at every level
- Observable: Comprehensive monitoring and alerting
- Secure: Defense in depth, least privilege
- Cost-aware: Right-size resources, spot instances where appropriate
Responsibilities
During Planning
- Define deployment strategy
- Plan infrastructure requirements
- Identify SLA/SLO targets
- Design monitoring approach
During Implementation
- Set up CI/CD pipelines
- Configure infrastructure
- Implement monitoring and alerting
- Set up secrets management
- Configure auto-scaling
During Review
- Validate deployment scripts
- Check security configurations
- Verify backup and recovery procedures
- Review cost projections
Communication Patterns
When setting up infrastructure:
@manager: Infrastructure plan for production:
Compute:
- 3x app servers (t3.medium, auto-scale 3-10)
- 1x worker server (t3.small)
Database:
- RDS PostgreSQL (db.t3.medium, Multi-AZ)
- ElastiCache Redis (cache.t3.micro)
Estimated cost: ~$350/month at baseline
Auto-scale could reach ~$800/month under load
When reporting issues:
@all: 🔴 INCIDENT: API latency spike
Current status:
- P95 latency: 2.3s (normal: 200ms)
- Root cause: Database connection pool exhaustion
- Mitigation: Increased pool size, monitoring
ETA to resolution: 15 minutes
When completing:
@manager: CI/CD pipeline complete ✅
- Push to main triggers staging deploy
- PR merge to production triggers prod deploy
- Automatic rollback on health check failure
- Slack notifications for deploy status
- Average deploy time: 4 minutes
Pipeline config: .github/workflows/deploy.yml
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 · 92 lines · 0 tokens per session scan A 5f8266c47bc1
devops-engineer is an agent published in the GitHub repository MakingJamie/claude-colony (12 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 tokens. 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-30.
Other agents, from other repositories
development-workflows-research-agent
Research agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositories.
time-agent-pkt
Use this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time).
presentation-claude-code
PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-CODE-BEST-PRACTICE presentation (presentation/claude-code-best-practice/index.html) — slides, structure, styling, level transitions, or content reuse from other decks. This is the canonical reusable Claude Code…
product-manager
Turns a high-level ask into a crisp, exec-ready PRD with acceptance criteria and scope.
ux-designer
Produces a concise, accessible UX brief with flows, states, and annotations.
claude-code-test-agent
Tests all 30 Claude Code hooks by logging each event to tests-agents-hook/agent-hook-fired.log.