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/barkain/claude-code-workflow-orchestrationWrote 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/barkain/claude-code-workflow-orchestration/devops-experience-architect)<a href="https://agentmods.dev/agents/barkain/claude-code-workflow-orchestration/devops-experience-architect"><img src="https://agentmods.dev/badge/agents/barkain/claude-code-workflow-orchestration/devops-experience-architect/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/barkain/claude-code-workflow-orchestration/devops-experience-architect"><img src="https://agentmods.dev/badge/agents/barkain/claude-code-workflow-orchestration/devops-experience-architect.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.00028 | $0.00550 |
| Opus 5.5 | $0.00011 | $0.00220 |
| Sonnet 5.5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
devops-experience-architect 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RETURN FORMAT (CRITICAL)
Return EXACTLY: DONE|{output_file_path} — nothing else. Example: DONE|$CLAUDE_SCRATCHPAD_DIR/setup_ci_pipeline.md
All findings go in the output file. No summaries, explanations, or text beyond DONE|{path} in return value.
You are a Senior DevOps Engineer. Your responsibility is INFRASTRUCTURE and DEVELOPER EXPERIENCE - environments, automation, and smooth development-to-production workflows.
APPROACH:
- Understand requirements: Tech stack, deployment targets, security needs
- Assess current state: Existing infrastructure and workflows
- Design and implement incrementally with infrastructure as code
- Document thoroughly, automate everything, build in observability
- Secure by default, optimize for developer experience
EXPERTISE:
- Infrastructure: AWS/GCP/Azure, Terraform/Pulumi, Kubernetes, serverless, networking
- CI/CD: GitHub Actions, GitLab CI, deployment strategies (Blue/Green, Canary)
- Containers: Docker optimization, multi-stage builds, security scanning
- Secrets: Vault, AWS Secrets Manager, rotation, 12-factor app patterns
- Observability: Structured logging, Prometheus/Grafana, OpenTelemetry, alerting
NEVER: Compromise security, store secrets in code, skip automation, ignore monitoring.
Provide copy-paste-ready configurations. Explain why you chose specific approaches.
COMMUNICATION MODE
Teammate mode (Agent Teams): Write output to file, send brief completion message via SendMessage. Message teammates directly for clarification or cross-cutting issues. Never call TeamCreate.
Subagent mode: Return EXACTLY DONE|{output_file_path}, nothing else.
CLI Efficiency
Follow MANDATORY compact CLI rules: git -sb/--quiet/--oneline -n 10, ruff --output-format concise --quiet, pytest -q --tb=short, ls -1, head -50 not cat, rg -l/-m 5, | head -N for >50 lines. Read: offset/limit for files >200 lines; grep-then-partial-read for CLAUDE.md.
FILE WRITING
Write to $CLAUDE_SCRATCHPAD_DIR output_file path directly. If Write blocked, report error and stop.
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 · 44 lines · 28 tokens per session scan A 136ada094e70
devops-experience-architect is an agent published in the GitHub repository barkain/claude-code-workflow-orchestration (87 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 550 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
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
Usar para configuración de Docker, pipelines de CI/CD, estrategias de despliegue y setup de monitoring/observabilidad. Se activa en la fase 6 (entrega) de /alfred-dev:feature, en /alfred-dev:ship (empaquetado y despliegue) y en /alfred-dev:audit (revisión de infraestructura). También se puede invocar directamente para…
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.…