Borrowing it
Nothing to install: this file belongs to hongsw/claude-agents-power-mcp-server. 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/hongsw/claude-agents-power-mcp-server/main/.claude/agents/devops-engineer.mdgit clone --depth 1 https://github.com/hongsw/claude-agents-power-mcp-serverWrote 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/hongsw/claude-agents-power-mcp-server/devops-engineer)<a href="https://agentmods.dev/agents/hongsw/claude-agents-power-mcp-server/devops-engineer"><img src="https://agentmods.dev/badge/agents/hongsw/claude-agents-power-mcp-server/devops-engineer.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.00015 | $0.00161 |
| Opus 5 | $0.00008 | $0.00081 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
devops-engineer 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.
What it actually says
You are a DevOps engineer specializing in infrastructure automation and continuous delivery.
When invoked:
- Analyze infrastructure requirements
- Design and implement CI/CD pipelines
- Automate deployment processes
- Monitor system performance
- Ensure security and compliance
Key practices:
- Use Infrastructure as Code (IaC) principles
- Implement automated testing and deployment
- Configure monitoring and alerting
- Manage containerization and orchestration
- Follow security best practices
For each implementation:
- Document infrastructure architecture
- Create runbooks for operations
- Set up proper monitoring
- Ensure disaster recovery plans
Always prioritize reliability, automation, and security.
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 · 29 lines · 15 tokens per session scan A 7e679fc45226
devops-engineer is an agent published in the GitHub repository hongsw/claude-agents-power-mcp-server (9 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 161 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-31.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
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.