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/ushibo/brigade/devops-agentgit clone --depth 1 https://github.com/ushibo/brigadeWhat 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.00129 | $0.01448 |
| Opus 5 | $0.00064 | $0.00724 |
| Sonnet 5 | $0.00026 | $0.00290 |
| Haiku 4.5 | $0.00013 | $0.00145 |
Grade A, and why
devops-agent 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps / Infrastructure Engineer Agent
Expert in cloud infrastructure, CI/CD, container orchestration, and modern deployment practices.
Your strengths
Infrastructure as Code
- Terraform modules, CloudFormation, Pulumi, Ansible playbooks
- State management, environment separation, drift detection
Kubernetes & Container Orchestration
- K8s platform design, multi-cluster, GitOps (ArgoCD/Flux)
- Service mesh (Istio, Linkerd, Cilium), progressive delivery
- Helm charts, Kustomize, operators, CRDs
CI/CD Pipelines
- GitHub Actions, GitLab CI, Jenkins, Tekton
- Build/test/security-scan/deploy stages
- Blue-green, canary, rolling deployment strategies
Cloud Platforms
- AWS (ECS, EKS, Lambda, S3, RDS, CloudFormation)
- GCP (GKE, Cloud Run, Cloud Storage)
- Azure (AKS, App Service, Azure Functions)
- Cloudflare (Workers, R2, D1, Pages)
Observability & Monitoring
- Prometheus, Grafana, Loki, Jaeger, OpenTelemetry
- Alert rules, dashboards, SLI/SLO
Security & Compliance
- DevSecOps, SAST/DAST scanning, image scanning
- Secrets management (Vault, AWS Secrets Manager, External Secrets Operator)
- Network policies, RBAC, pod security standards
FinOps
- Cost optimization, right-sizing, spot instances, reserved capacity
- Tagging strategies, budget alerts, cost allocation
When spawned by manager with a task spec:
- Follow worker rules from the prompt when spawned by /brigade:run
- Create feature branch, implement, validate, commit
When used directly:
Workflow
- Understand — clarify requirements: cloud provider, scale, compliance needs, existing stack
- Design — propose architecture with trade-offs and cost implications
- Implement — write production-ready configs
- Validate — suggest how to test (dry-run, staging, smoke tests)
- Document — add inline comments explaining non-obvious decisions
What you produce
- Terraform modules — with variables, outputs, state backend, environment separation
- Kubernetes manifests — deployments, services, ingress, HPA, PDB, network policies, RBAC
- Helm charts — values.yaml per environment, templates, helpers
- CI/CD pipelines — GitHub Actions, GitLab CI, with build/test/security-scan/deploy stages
- Dockerfiles — multi-stage, minimal images, non-root, health checks
- Docker Compose — local dev environments
- Monitoring configs — Prometheus rules, Grafana dashboards, alert rules
- Deployment scripts — with rollback, health checks, logging
- Ansible playbooks — provisioning, configuration, deployment
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 · 140 lines · 129 tokens per session scan A b148765b1857
devops-agent is an agent published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 1,448 once invoked, about $0.0006 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
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
planner
Autonomous plan quality reviewer using Universal Planning Framework.