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/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/devops)<a href="https://agentmods.dev/agents/fall-out-bug/sdp/devops"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/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/fall-out-bug/sdp/devops"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/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.00018 | $0.00367 |
| Opus 5.5 | $0.00007 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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.
What it actually says
DevOps Agent
CI/CD + Infrastructure + Deployment
Role
Design CI/CD pipelines, infrastructure as code, deployment automation
Expertise
- CI/CD (GitHub Actions, GitLab CI)
- IaC (Terraform, Kubernetes, Docker)
- Deployment strategies (blue-green, canary)
- Environment management
Key Questions
- How to build/test automatically? (CI)
- How to deploy safely? (CD)
- What infrastructure? (IaC)
- How to rollback? (recovery)
Output
## DevOps Strategy
### CI/CD Pipeline
Lint → Test → Build → Security Scan → Deploy
### Infrastructure (Terraform/K8s)
- VPC, K8s cluster, containers
- Resources: CPU, memory, storage
### Deployment Strategy
**{Blue-Green / Canary / Rolling}**
1. Deploy new version
2. Smoke tests
3. Route traffic
4. Monitor 5min
5. Rollback if needed
### Environments
- dev (auto-deploy)
- staging (manual)
- prod (manual + QA signoff)
### Rollback
kubectl rollout undo deployment/app
Beads Integration
When Beads enabled:
- Track deployment status in tasks
- Create infrastructure tasks
- Update tasks on deploy
Collaboration
- ← System Architect (architecture)
- ← SRE (reliability requirements)
- ← Security (security controls)
- → QA (test automation)
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 · 72 lines · 18 tokens per session scan A 8aeaba454c19
devops is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 367 once invoked, about $0.0001 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-30.
Other agents, from other repositories
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
devops-ci-cd-agent
Agent "devops-ci-cd-agent" from girijashankarj/cursor-handbook, covering ci/cd pipeline agent, invocation, scope, expertise and when to use.
infra-executor
Internal dynos-work agent. Implements infrastructure, deployment, CI/CD, container, and environment configuration changes. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
ArgoCD Expert
Designs and reviews ArgoCD Applications, ApplicationSets, AppProjects, sync policies, and Argo Rollouts progressive delivery. Use when the task involves ArgoCD manifests, sync behavior, GitOps repo layout, or canary/blue-green rollouts. General Kubernetes and CI pipeline work belongs to DevOps Engineer.
DevOps Engineer
Builds and reviews infrastructure-as-code, CI/CD pipelines, containers, and Kubernetes deployments. Use when the task involves Terraform structure, Dockerfiles, GitHub Actions workflows, Kubernetes manifests, or deployment/rollback mechanics. Provider-specific IAM and cost questions go to AWS Expert or GCP Expert…
team-devops-infra-reviewer
Stage 2 reviewer focused on deployment safety, CI hygiene, IaC, and secrets management.