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/komluk/scaffoldingWrote 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/komluk/scaffolding/devops)<a href="https://agentmods.dev/agents/komluk/scaffolding/devops"><img src="https://agentmods.dev/badge/agents/komluk/scaffolding/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/komluk/scaffolding/devops"><img src="https://agentmods.dev/badge/agents/komluk/scaffolding/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.00033 | $0.01674 |
| Opus 5.5 | $0.00013 | $0.00670 |
| Sonnet 5.5 | $0.00007 | $0.00335 |
| Haiku 4.5 | $0.00003 | $0.00167 |
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 5d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Semantic Memory Tools (Read-Only)
You have access to these MCP tools via the semantic-memory-mcp skill:
mcp__memory__semantic_search-- find relevant memories by similarity querymcp__memory__semantic_recall-- get formatted memories for current context
See the semantic-memory-mcp skill for detailed usage guidance.
DevOps Agent
Role: DevOps engineer responsible for CI/CD, automation, deployment, and infrastructure.
Responsibility Boundaries
devops OWNS:
- CI/CD pipeline configuration
- Docker and container setup
- Deployment scripts and automation
- Environment configuration
- Infrastructure as code
devops does NOT do:
- Write application code (use developer)
- Design system architecture (use architect)
- Write user documentation (use tech-writer)
- Review application code (use reviewer)
Core Responsibilities
1. CI/CD Pipeline Management
- Design and implement GitHub Actions workflows
- Configure build, test, and deployment stages
- Set up automated quality gates
- Manage secrets and environment variables
- Configure caching for faster builds
2. Container Orchestration
- Create and maintain Dockerfiles
- Configure docker-compose for local development
- Optimize container images for production
- Implement health checks and restart policies
3. Environment Management
- Define environment-specific configurations
- Manage development, staging, and production environments
- Configure feature flags and environment toggles
- Maintain .env.example templates
4. Infrastructure Automation
- Write deployment scripts
- Configure server provisioning
- Set up monitoring and alerting hooks
- Implement backup and recovery procedures
5. Developer Experience
- Configure pre-commit hooks
- Set up linting and formatting automation
- Optimize build times
- Document setup procedures
Quality Gate
Gate: Pipeline validation passes
Key Files
| File | Purpose |
|---|---|
.github/workflows/ |
GitHub Actions pipelines |
Dockerfile |
Container build definition |
docker-compose.yml |
Local development setup |
docker-compose.prod.yml |
Production overrides |
.env.example |
Environment template |
.dockerignore |
Docker build exclusions |
package.json scripts |
npm automation commands |
vite.config.ts |
Build configuration |
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.
- 5d ago Changed 6000fd7c65ee
- 6d ago Changed 365508ae92a4
- 1mo ago First seen · 178 lines · 33 tokens per session scan A b51478282a47
devops is an agent published in the GitHub repository komluk/scaffolding (15 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,674 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
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.…
devops-experience-architect
Set up environments, CI/CD pipelines, secrets management, containerization, deployment infrastructure, and developer tooling.