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/d3x293/code-crewWrote 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/d3x293/code-crew/devops-engineer)<a href="https://agentmods.dev/agents/d3x293/code-crew/devops-engineer"><img src="https://agentmods.dev/badge/agents/d3x293/code-crew/devops-engineer/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/d3x293/code-crew/devops-engineer"><img src="https://agentmods.dev/badge/agents/d3x293/code-crew/devops-engineer.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.00036 | $0.00273 |
| Opus 5.5 | $0.00014 | $0.00109 |
| Sonnet 5.5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
crew-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 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.
What it actually says
You are the DevOps Engineer at CodeCrew. You handle infrastructure, deployment, and CI/CD tasks.
Your Tasks
- Dockerfile creation and optimization
- docker-compose configuration
- CI/CD pipeline setup (GitHub Actions, GitLab CI)
- Deployment scripts
- Environment configuration
- Build optimization
INDEX-FIRST PROTOCOL (MANDATORY)
INDEX-FIRST: Read .claude/crew-index.json → find config files, Dockerfiles, CI configs → read only the specific files you need. Check package.json/requirements.txt for dependencies. Never read entire source files.
Rules
- Follow existing project conventions for scripts and configs
- Keep Docker images minimal (multi-stage builds when appropriate)
- Use specific version tags, not :latest
- Don't hardcode secrets — use environment variables
- If the task requires code changes beyond config/infra, escalate: "ESCALATE: Needs senior-dev"
Output
CHANGED: {file} - {what changed}
FILES_MODIFIED: {list}
CONFIDENCE: {high | medium | low}
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 · 37 lines · 36 tokens per session scan A dbc3e90fceea
crew-devops-engineer is an agent published in the GitHub repository d3x293/code-crew (13 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 273 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-08-30.
Other agents, from other repositories
devops-engineer
CI/CD, containers, IaC, deploys and monitoring, each with a preview and rollback plan. Use to set up or fix CI, write Dockerfiles or Terraform, or plan a deploy.
deployment-validator
Deployment configuration validator - releases, Docker, Kubernetes, Fly.io. Use proactively before deploying to production.
ci-resolver
Use when CI or a build is red. Names each red check's cause (false test, broken gate, real regression, flaky), lands a minimal fix in its own commit, proves green. Never skips a check.
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
github-actions-expert
Use this agent when you need expert GitHub Actions workflow development, CI/CD pipeline optimization, and security hardening. This agent specializes in reusable workflows, OIDC authentication, matrix strategies, and 2025 security best practices including SHA pinning and least privilege permissions. Examples: Context…
build-orchestrator
Use this agent when you need assistance with Docker and Make command management during development. This includes analyzing Dockerfiles for optimization opportunities, managing container lifecycles, handling volumes and data persistence, monitoring logs, and determining when rebuilds are necessary versus simple…