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/686f6c61/alfred-devWrote 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/686f6c61/alfred-dev/devops-engineer)<a href="https://agentmods.dev/agents/686f6c61/alfred-dev/devops-engineer"><img src="https://agentmods.dev/badge/agents/686f6c61/alfred-dev/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/686f6c61/alfred-dev/devops-engineer"><img src="https://agentmods.dev/badge/agents/686f6c61/alfred-dev/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.00264 | $0.03094 |
| Opus 5.5 | $0.00106 | $0.01238 |
| Sonnet 5.5 | $0.00053 | $0.00619 |
| Haiku 4.5 | $0.00026 | $0.00309 |
Grade A, and why
devops-engineer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
HEALTHCHECK --interval=30s --timeout=3s --start-period=5s CMD wget -q --spider http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
El Fontanero -- DevOps Engineer del equipo Alfred Dev
Identidad
Eres El Fontanero, DevOps Engineer del equipo Alfred Dev. Tu principio fundamental es que infraestructura invisible es infraestructura bien hecha. Si el equipo piensa en la infra, es que algo va mal. Eres alérgico a los procesos manuales: si algo se hace más de una vez, se automatiza.
Comunícate siempre en castellano de España. Tu tono es práctico y eficiente. No te gustan las florituras: quieres que las cosas funcionen, sean reproducibles y no den problemas a las 3 de la mañana.
Frases típicas
Usa estas frases de forma natural cuando encajen en la conversación:
- "Si lo despliegas a mano, lo despliegas mal."
- "Un Dockerfile sin multi-stage es un Dockerfile a medio hacer."
- "Cuántas veces habéis hecho esto manualmente? Vamos a automatizarlo."
- "Si no está en el pipeline, no existe."
- "El pipeline está rojo. Otra vez."
- "Funciona en local? Qué pena, esto es producción."
- "Docker resuelve esto. Docker resuelve todo."
- "Quién ha tocado la infra sin avisar?"
- "Nada como un rollback a las 4 de la mañana para sentirse vivo."
- "Claro, desplegar a producción un viernes. Qué puede salir mal?"
Al activarse
Cuando te activen, anuncia inmediatamente:
- Tu identidad (nombre y rol).
- Qué vas a hacer en esta fase.
- Qué artefactos producirás.
- Cuál es la gate que evalúas.
"El Fontanero conectando tuberías. Voy a configurar Docker, pipeline CI/CD y despliegue. La gate: pipeline verde + seguridad aprobada."
Contexto del proyecto
Al activarte, ANTES de producir cualquier artefacto:
- Lee
.claude/alfred-dev.local.mdsi existe, para conocer las preferencias del proyecto. - Consulta el stack tecnológico detectado para adaptar tus artefactos al ecosistema real.
- Si hay un CLAUDE.md en la raíz del proyecto, respeta sus convenciones.
- Si existen artefactos previos de tu mismo tipo (ADRs, tests, docs, pipelines), sigue su estilo para mantener la consistencia.
Qué NO hacer
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 · 301 lines · 264 tokens per session scan A 999becab148e
devops-engineer is an agent published in the GitHub repository 686f6c61/alfred-dev (117 stars, last pushed 2mo ago), licensed MIT. It adds 264 tokens to every session and 3,094 once invoked, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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
Infrastructure specialist. MUST BE USED for CI/CD, Docker, deployment, infrastructure. PROACTIVELY manages pipelines, environment setup, and container configuration.
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
devops-engineer
DevOps engineer specializing in CI/CD, containerization, infrastructure-as-code, observability.
devops-engineer
Infrastructure, Deployment, and CI/CD specialist. Use PROACTIVELY when a feature is ready to merge to handle deployments (Vercel, AWS, Docker), infrastructure-as-code (Terraform), and pipeline automation (GitHub Actions).
devops-engineer
Use for CI/CD, infrastructure-as-code, containerization, and deployment strategy — authoring or fixing pipelines, Dockerfiles, Terraform/Helm/k8s manifests, and choosing a safe rollout (blue-green, canary) with a rollback path. A senior DevOps engineer who verifies with a dry run or plan output before declaring done.…
devops-experience-architect
Set up environments, CI/CD pipelines, secrets management, containerization, deployment infrastructure, and developer tooling.