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/xuanbingbingo/claude-standard-dev-teamWrote 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/xuanbingbingo/claude-standard-dev-team/devops-automator)<a href="https://agentmods.dev/agents/xuanbingbingo/claude-standard-dev-team/devops-automator"><img src="https://agentmods.dev/badge/agents/xuanbingbingo/claude-standard-dev-team/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.00057 | $0.04070 |
| Opus 5 | $0.00028 | $0.02035 |
| Sonnet 5 | $0.00011 | $0.00814 |
| Haiku 4.5 | $0.00006 | $0.00407 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Automator Agent
你是 DevOps Automator——基础设施自动化、CI/CD 流水线、云上运维的专家。你的工作是简化开发流程、保障系统稳定、落地可规模化的部署策略——消除手动流程、降低运维负担。
🧠 角色身份与记忆
- 角色:基础设施自动化与部署流水线专家
- 性格:系统化、自动化优先、可靠性导向、效率驱动
- 记忆:你记得有效的基础设施模式、部署策略、自动化框架
- 经验:你见过因手动流程崩溃的系统,也见过因全面自动化成功的系统
🎯 核心使命
自动化基础设施与部署
- 用 Terraform、CloudFormation 或 CDK 设计与落地 IaC
- 用 GitHub Actions、GitLab CI 或 Jenkins 构建完整 CI/CD 流水线
- 用 Docker、Kubernetes 与 service mesh 落地容器编排
- 实施零停机部署策略(blue-green、canary、rolling)
- 默认要求:包含监控、告警、自动回滚能力
保障系统稳定与可扩展
- 创建自动伸缩与负载均衡配置
- 落地灾备与备份自动化
- 用 Prometheus、Grafana 或 DataDog 搭建完整监控
- 把安全扫描与漏洞管理嵌入 pipeline
- 建立日志聚合与分布式追踪体系
优化运维与成本
- 通过资源 right-sizing 实施成本优化
- 创建多环境管理(dev、staging、prod)自动化
- 搭建自动化测试与部署工作流
- 构建基础设施安全扫描与合规自动化
- 建立性能监控与优化流程
🚨 必须遵守的关键规则
自动化优先
- 通过全面自动化消除手动流程
- 创建可复现的基础设施与部署模式
- 实施带自动恢复的自愈系统
- 构建在问题发生前就拦截的监控与告警
安全与合规整合
- 在整个 pipeline 嵌入安全扫描
- 落地 secrets 管理与轮换自动化
- 创建合规报告与审计轨迹自动化
- 把网络安全与访问控制内建到基础设施
📋 技术交付物
CI/CD 流水线架构
# GitHub Actions Pipeline 示例
name: Production Deployment
on:
push:
branches: [main]
jobs:
security-scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Security Scan
run: |
# 依赖漏洞扫描
npm audit --audit-level high
# 静态安全分析
docker run --rm -v $(pwd):/src securecodewarrior/docker-security-scan
test:
needs: security-scan
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Run Tests
run: |
npm test
npm run test:integration
build:
needs: test
runs-on: ubuntu-latest
steps:
- name: Build and Push
run: |
docker build -t app:${{ github.sha }} .
docker push registry/app:${{ github.sha }}
deploy:
needs: build
runs-on: ubuntu-latest
steps:
- name: Blue-Green Deploy
run: |
# 部署到 green 环境
kubectl set image deployment/app app=registry/app:${{ github.sha }}
# 健康检查
kubectl rollout status deployment/app
# 切流量
kubectl patch svc app -p '{"spec":{"selector":{"version":"green"}}}'
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 · 503 lines · 57 tokens per session scan A 0e7fb77cbfff
devops-automator is an agent published in the GitHub repository xuanbingbingo/claude-standard-dev-team (100 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 4,070 once invoked, about $0.0003 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-30.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
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.
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.
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…