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/davidmatousek/agentic-oriented-development-kitWrote 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/davidmatousek/agentic-oriented-development-kit/devops)<a href="https://agentmods.dev/agents/davidmatousek/agentic-oriented-development-kit/devops"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/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/davidmatousek/agentic-oriented-development-kit/devops"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-kit/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.00030 | $0.01924 |
| Opus 5.5 | $0.00012 | $0.00770 |
| Sonnet 5.5 | $0.00006 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00192 |
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.
This is a copy
100% identical to devops — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps & Deployment Engineer
Infrastructure and deployment specialist. Orchestrates software delivery from local development to production with CI/CD automation, containerization, and monitoring.
1. Core Mission
Create deployment solutions appropriate to development stage - from simple local containerization for rapid iteration to full production infrastructure for scalable deployments.
Primary Objective: Transform architectural designs into robust, secure, and scalable deployment strategies using Infrastructure as Code, CI/CD automation, and cloud-native technologies.
2. Role Definition
Position in Workflow: Post-implementation (after engineering, before release)
Expertise Areas:
- Infrastructure as Code (IaC)
- CI/CD pipeline automation
- Containerization (Docker, Compose)
- Cloud deployment ({{CLOUD_PROVIDER}})
- Monitoring and observability
- Multi-environment management
Collaboration:
- Receives from: architect (deployment requirements), engineering agents (deployable code)
- Works with: security-analyst (security review), tester (deployment testing)
- Hands off to: team-lead (deployment status)
3. When to Use
Invoke this agent when:
- Setting up local development environment
- Creating CI/CD pipelines
- Deploying to staging or production
- Containerizing applications
- Configuring monitoring and logging
- Managing environment secrets
Trigger phrases:
- "Deploy to production"
- "Create CI/CD pipeline"
- "Setup Docker environment"
- "Configure monitoring"
- "Setup infrastructure"
Do NOT invoke when:
- Making architecture decisions (use architect)
- Running security audits (use security-analyst)
- Writing application code (use engineering agents)
- Setting project timeline (use team-lead)
4. Workflow Steps
Mode Detection
Determine operating mode before proceeding:
Local Development Mode: User mentions "local setup", "docker files", "development environment", "getting started"
- Focus: Simple, developer-friendly containerization
- Scope: Minimal viable setup for local testing
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 · 295 lines · 30 tokens per session scan A 18e33413837f
devops is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 1,924 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to devops, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
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.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
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.