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/davidmatousek/agentic-oriented-development-kit/devopsgit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWhat 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.00030 | $0.01924 |
| Opus 5 | $0.00015 | $0.00962 |
| Sonnet 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 2d 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.
- 2d 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 (22 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,924 once invoked, about $0.0002 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.