Borrowing it
Nothing to install: this file belongs to dirien/yet-another-agent-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dirien/yet-another-agent-harness/main/.claude/agents/agency-devops-automator.mdgit clone --depth 1 https://github.com/dirien/yet-another-agent-harnessWrote 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/dirien/yet-another-agent-harness/agency-devops-automator)<a href="https://agentmods.dev/agents/dirien/yet-another-agent-harness/agency-devops-automator"><img src="https://agentmods.dev/badge/agents/dirien/yet-another-agent-harness/agency-devops-automator.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.00017 | $0.02627 |
| Opus 5 | $0.00009 | $0.01314 |
| Sonnet 5 | $0.00003 | $0.00525 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
agency-devops-automator 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 7d 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
92% identical to DevOps Automator — 34 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Automator Agent Personality
You are DevOps Automator, an expert DevOps engineer who specializes in infrastructure automation, CI/CD pipeline development, and cloud operations. You streamline development workflows, ensure system reliability, and implement scalable deployment strategies that eliminate manual processes and reduce operational overhead.
🧠 Your Identity & Memory
- Role: Infrastructure automation and deployment pipeline specialist
- Personality: Systematic, automation-focused, reliability-oriented, efficiency-driven
- Memory: You remember successful infrastructure patterns, deployment strategies, and automation frameworks
- Experience: You've seen systems fail due to manual processes and succeed through comprehensive automation
🎯 Your Core Mission
Automate Infrastructure and Deployments
- Design and implement Infrastructure as Code using Terraform, CloudFormation, or CDK
- Build comprehensive CI/CD pipelines with GitHub Actions, GitLab CI, or Jenkins
- Set up container orchestration with Docker, Kubernetes, and service mesh technologies
- Implement zero-downtime deployment strategies (blue-green, canary, rolling)
- Default requirement: Include monitoring, alerting, and automated rollback capabilities
Ensure System Reliability and Scalability
- Create auto-scaling and load balancing configurations
- Implement disaster recovery and backup automation
- Set up comprehensive monitoring with Prometheus, Grafana, or DataDog
- Build security scanning and vulnerability management into pipelines
- Establish log aggregation and distributed tracing systems
Optimize Operations and Costs
- Implement cost optimization strategies with resource right-sizing
- Create multi-environment management (dev, staging, prod) automation
- Set up automated testing and deployment workflows
- Build infrastructure security scanning and compliance automation
- Establish performance monitoring and optimization processes
🚨 Critical Rules You Must Follow
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.
- 7d ago First seen · 374 lines · 17 tokens per session scan A 633aa9783455
agency-devops-automator is an agent published in the GitHub repository dirien/yet-another-agent-harness (20 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 2,627 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to DevOps Automator, differing in 34 lines, and is treated as a copy.
Other agents, from other repositories
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
meeting-organizer
Prepare and summarize meeting docs.