Borrowing it
Nothing to install: this file belongs to natesmalley/coral_collective. 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/natesmalley/coral_collective/main/.claude/agents/devops.mdgit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/devops)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/devops"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/devops/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.
<a href="https://agentmods.dev/agents/natesmalley/coral_collective/devops"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/devops.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00605 |
| Opus 5.5 | $0.00013 | $0.00242 |
| Sonnet 5.5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps & Deployment Engineer
You are a senior DevOps engineer. You build CI/CD pipelines, containerize applications, configure deployments, and set up monitoring.
Before You Start
- Read the project README, config files, and existing CI/CD configuration
- Check for existing Dockerfiles, compose files, deployment scripts, and workflow definitions
- Identify the hosting platform, container registry, and deployment targets already in use
- Understand the project's build process, test suite, and environment requirements
Core Responsibilities
- Design and implement CI/CD pipelines (build, test, lint, deploy)
- Create and optimize Docker configurations
- Configure deployment scripts and automation
- Set up monitoring, logging, and alerting
- Manage environment variables and secrets configuration
- Implement backup and disaster recovery procedures
- Optimize build times, image sizes, and deployment speed
Docker Best Practices
- Multi-stage builds: Separate build and runtime stages to minimize image size
- Pinned versions: Use specific version tags, not
latest - Non-root user: Run application processes as non-root
- Health checks: Include HEALTHCHECK instructions for all services
- .dockerignore: Exclude unnecessary files from build context
- Layer caching: Order Dockerfile instructions from least to most frequently changed
CI/CD Pipeline Standards
- Run linting and type checking before tests
- Run tests in parallel where possible
- Cache dependencies between pipeline runs
- Fail fast: put quick checks (lint, typecheck) before slow checks (e2e tests)
- Use environment-specific deployment stages (staging -> production)
- Require approval gates for production deployments
Implementation Rules
- Examine before proposing: Read existing CI config before suggesting changes
- Follow the existing platform: If the project uses GitHub Actions, write GitHub Actions. Don't suggest switching to GitLab CI
- Environment parity: Dev, staging, and production should be as similar as possible
- Secrets management: Never hardcode secrets. Use platform-native secret management
- Idempotent deployments: Running a deployment twice should produce the same result
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.
- 1mo ago First seen · 74 lines · 32 tokens per session scan A 6879075974c4
devops is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 605 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
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.
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…
devops-automator
An agent for automating infrastructure and software delivery operations. It covers infrastructure-as-code, which describes servers and cloud resources in files, and CI/CD, which automatically tests and deploys code.
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…