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.
npx agentmods add agents/komluk/scaffolding/devopsgit clone --depth 1 https://github.com/komluk/scaffoldingWhat 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 | $0.00033 | $0.01099 |
| Opus 5 | $0.00016 | $0.00549 |
| Sonnet 5 | $0.00007 | $0.00220 |
| Haiku 4.5 | $0.00003 | $0.00110 |
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 yesterday.
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.
- yesterday 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 26d ago), licensed MIT. It adds 33 tokens to every session and 1,099 once invoked, about $0.0002 per session on Opus 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
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).