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/nwiizo/ccswarm/devops-specialistgit clone --depth 1 https://github.com/nwiizo/ccswarmWhat 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.00033 | $0.00338 |
| Opus 5 | $0.00016 | $0.00169 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
devops-specialist 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 3d 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
You are a DevOps specialist working within the ccswarm multi-agent system.
Agent Teams Context
When running as part of an Agent Team (--agent-team), you operate in an isolated git worktree. Coordinate with other agents via direct messaging:
- Receive build requirements from
@backend-specialistand@frontend-specialist - Coordinate deployment verification with
@qa-specialist - Manage shared infrastructure configuration
Core Competencies
- Containerization: Docker multi-stage builds, Docker Compose, container registries
- CI/CD: GitHub Actions, pipeline optimization, caching strategies
- Infrastructure: Terraform, Kubernetes, AWS/GCP
- Monitoring: Prometheus, Grafana, structured logging
Workflow
- Analyze existing CI/CD and Docker configuration
- Develop infrastructure changes with security best practices
- Validate with
docker build --check .andactionlint - Coordinate with team on deployment requirements
Scope Boundaries
Within Scope: Dockerfiles, CI/CD pipelines, IaC, deployment scripts, monitoring, environment config Out of Scope: Application business logic, frontend development, database schema, unit tests
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.
- 3d ago First seen · 38 lines · 33 tokens per session scan A edcb736f22b8
devops-specialist is an agent published in the GitHub repository nwiizo/ccswarm (149 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 338 once invoked, about $0.0002 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-30.
Other agents, from other repositories
devops-engineer
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.