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/ushibo/brigadeWrote 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/ushibo/brigade/devops-agent)<a href="https://agentmods.dev/agents/ushibo/brigade/devops-agent"><img src="https://agentmods.dev/badge/agents/ushibo/brigade/devops-agent/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/ushibo/brigade/devops-agent"><img src="https://agentmods.dev/badge/agents/ushibo/brigade/devops-agent.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.00129 | $0.01448 |
| Opus 5.5 | $0.00052 | $0.00579 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 3mo ago), licensed MIT. It adds 129 tokens to every session and 1,448 once invoked, about $0.0005 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
ci-resolver
Use when CI or a build is red. Names each red check's cause (false test, broken gate, real regression, flaky), lands a minimal fix in its own commit, proves green. Never skips a check.
github-actions-expert
Use this agent when you need expert GitHub Actions workflow development, CI/CD pipeline optimization, and security hardening. This agent specializes in reusable workflows, OIDC authentication, matrix strategies, and 2025 security best practices including SHA pinning and least privilege permissions. Examples: Context…
deployment-expert
Specializes in Vercel deployment strategies, CI/CD pipelines, preview URLs, production promotions, rollbacks, environment variables, and domain configuration. Use when troubleshooting deployments, setting up CI/CD, or optimizing the deploy pipeline.
deploio-cli
Executes Deploio CLI operations via nctl on behalf of coordinator skills — creating and updating apps, resolving git credentials, monitoring builds and deployments, provisioning backing services, and managing CI/CD service accounts. Spawned by deploio-deploy, deploio-manage, deploio-debug, deploio-provision, and…
mlops-pm
Authors the model deployment, monitoring, drift detection, and incident-response plan. PM-side counterpart to engineering's mlops-reviewer. Specifies what is monitored, what triggers alerts, and what the rollback procedure is.
production
Production readiness audit specialist for repo-doctor. Audits operability - CI/CD, config, error handling, observability, licensing - returning scored JSON findings.