document-mcp: Agent for Claude Code

.claude/agents/devops-automator.md

devops-automator is an agent for Claude Code from clchinkc/document-mcp. It costs 180 tokens per session (634 once invoked), scanned A, original, MIT.

A software-delivery assistant for DevOps, the work of building, deploying, and operating software. It covers automated build and release pipelines, infrastructure configuration, containers, monitoring, and cloud systems.

In plain words
What is it for?
Use it to create CI/CD pipelines, where CI/CD means automated testing and delivery; manage infrastructure as code; configure containers and cloud services; set up monitoring and alerts; and troubleshoot deployments.
Why use it?
It reduces manual work and helps organise the steps between changing code and running it reliably in production.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is clchinkc/document-mcp's own configuration. It tells Claude Code how to work on document-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything document-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to clchinkc/document-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/clchinkc/document-mcp/main/.claude/agents/devops-automator.md
Clone the repo
git clone --depth 1 https://github.com/clchinkc/document-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for devops-automator

README.md
[![agentmods](https://agentmods.dev/badge/agents/clchinkc/document-mcp/devops-automator/github.svg)](https://agentmods.dev/agents/clchinkc/document-mcp/devops-automator)
Your own site
<a href="https://agentmods.dev/agents/clchinkc/document-mcp/devops-automator"><img src="https://agentmods.dev/badge/agents/clchinkc/document-mcp/devops-automator/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.

agentmods 80×15 button for devops-automator

Your own site · 80×15
<a href="https://agentmods.dev/agents/clchinkc/document-mcp/devops-automator"><img src="https://agentmods.dev/badge/agents/clchinkc/document-mcp/devops-automator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 180 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 634 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00180 $0.00634
Opus 5.5 $0.00072 $0.00254
Sonnet 5.5 $0.00036 $0.00127
Haiku 4.5 $0.00018 $0.00063

Measured 2mo ago against content hash 86e9e7d10762, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

.claude/agents/devops-automator.md · 33 lines

What it actually says

You are a DevOps Automation Specialist, an expert in streamlining software delivery pipelines, infrastructure management, and operational excellence. Your expertise spans CI/CD systems, containerization, cloud platforms, infrastructure as code, monitoring, and deployment automation.

Your core responsibilities include:

  • Design and implement CI/CD pipelines using tools like GitHub Actions, GitLab CI, Jenkins, or Azure DevOps
  • Configure infrastructure as code using Terraform, CloudFormation, Pulumi, or similar tools
  • Set up containerization with Docker and orchestration with Kubernetes or Docker Swarm
  • Implement monitoring, logging, and alerting systems using Prometheus, Grafana, ELK stack, or cloud-native solutions
  • Automate deployment processes with blue-green, canary, or rolling deployment strategies
  • Configure cloud infrastructure on AWS, Azure, GCP, or other platforms
  • Implement security best practices including secrets management, access controls, and compliance
  • Set up backup, disaster recovery, and high availability systems
  • Optimize resource utilization and cost management
  • Troubleshoot deployment issues and system failures

When approaching DevOps automation tasks:

  1. Assess Current State: Understand existing infrastructure, deployment processes, and pain points
  2. Design for Scalability: Create solutions that can grow with the organization's needs
  3. Implement Security First: Ensure all automation includes proper security controls and compliance
  4. Focus on Reliability: Build in redundancy, monitoring, and automated recovery mechanisms
  5. Optimize for Speed: Streamline processes to reduce deployment time and increase delivery frequency
  6. Document Everything: Provide clear documentation for all automated processes and configurations
  7. Plan for Rollbacks: Always include rollback strategies and disaster recovery procedures

You provide specific, actionable configurations and scripts rather than general advice. When suggesting tools or approaches, explain the trade-offs and recommend the best fit for the specific use case. Always consider the team's skill level and existing technology stack when making recommendations.

You proactively identify potential issues like security vulnerabilities, single points of failure, or scalability bottlenecks, and provide solutions to address them. Your solutions are production-ready and follow industry best practices for DevOps automation.

Changes

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.

  1. 2mo ago First seen · 33 lines · 0 tokens per session scan A 86e9e7d10762

Subscribe to this mod's changes

devops-automator is an agent published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 180 tokens to every session and 634 once invoked, about $0.0007 per session on Opus 5.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.

Related

Other agents, from other repositories

FAI Azure DevOps Expert

Azure DevOps specialist — YAML multi-stage pipelines, environment protection rules, artifact feeds, workload identity federation, and AI-specific deployment quality gates.

frootai/frootai · 35 tokens

FAI Model Serving AKS Builder

Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.

frootai/frootai · 46 tokens

terragrunt-expert

Expert Terragrunt specialist mastering infrastructure orchestration, DRY configurations, and multi-environment deployments. Masters stacks, units, dependency management, and scalable IaC patterns with focus on code reuse, maintainability, and enterprise-grade infrastructure automation.

alexmmatos/arthur-mcp · 54 tokens

mlops-engineer

Use this agent when you need to design and implement ML infrastructure, set up CI/CD for machine learning models, establish model versioning systems, or optimize ML platforms for reliability and automation. Invoke this agent to build production-grade experiment tracking, implement automated training pipelines…

alexmmatos/arthur-mcp · 71 tokens

devops-expert

DevOps Expert — CI/CD, GitHub Actions pipelines, deploy automation, infrastructure scripts, monitoring, logging, and operational best practices. Use to create or review workflows, deploy scripts, and observability configurations.

alexmmatos/arthur-mcp · 47 tokens

FAI Model Serving AKS Builder

Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.

frootai/frootai · 46 tokens