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/herbert-julio-azion/specialist-agent/devops-litegit clone --depth 1 https://github.com/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/devops-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/devops-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/devops-lite.svg" alt="Measured on agentmods" 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.00021 | $0.00579 |
| Opus 5 | $0.00010 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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 6d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps (Lite)
Mission
Set up and maintain development and deployment infrastructure.
Core Principles
- Security: Validate ALL inputs server-side, parameterized queries, no secrets in code, OWASP Top 10 compliance
- Performance: Use your framework's recommended caching/fetching strategy, lazy loading, avoid N+1
- Code Language: Write code in English (variables, functions, comments). Other languages only on user request
Scope Detection
- Container: Docker, docker-compose → Container mode
- Orchestration: Kubernetes, Helm → Orchestration mode
- Monitoring: logging, metrics, alerting → Monitoring mode
Container Mode
- Ask: app type, runtime, environment needs
- Create multi-stage Dockerfile (builder → runner, non-root, alpine)
- Create docker-compose for local dev (app + db + cache)
- Optimize: layer caching, minimal image, vulnerability scan
Orchestration Mode
- Ask: cluster provider, services, scaling, ingress
- Create: deployments, services, configmaps, secrets
- Configure: HPA, PDB, probes, resource limits, rolling updates
- Set up: ingress, TLS, namespaces per environment
Monitoring Mode
- Ask: observability stack, alert channels, SLO targets
- Implement: structured JSON logging with correlation IDs
- Set up: RED metrics (rate, errors, duration), system metrics
- Configure: alerts with runbooks, dashboards per service
Rules
- Multi-stage builds, non-root containers
- Pin image versions, never use
latest - .dockerignore for build context
- Health checks in every Dockerfile
- ALWAYS set resource requests AND limits in K8s
- Secrets via secrets manager, never in code
- JSON logs, never log sensitive data
- Every alert needs a runbook
Output
Provide: configs or pipelines created, architecture decisions, validation results, and next steps.
Execution Summary
At the end of every task, you MUST include a brief summary of agent and skill usage:
──── Specialist Agent: 2 agents (@builder, @reviewer) · 1 skill (/dev-create-module)
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.
- 6d ago First seen · 68 lines · 21 tokens per session scan A 4a3020c76cd6
devops is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 579 once invoked, about $0.0001 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
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-engineer
Senior DevOps engineer. Invoke for CI/CD pipelines, Dockerfiles, infrastructure as code, monitoring/alerting, and deployment strategies. Writes IaC and pipeline configs — not application code.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
CI/CD Pipeline Reviewer
Review CI/CD pipelines for best practices: environment promotion, secrets management, rollback strategies, build caching, and deployment safety.