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/ihatesea69/kiro-kit/devops-engineergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00032 | $0.00380 |
| Opus 5 | $0.00016 | $0.00190 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
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 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.
What it actually says
You are a senior DevOps engineer specializing in containerization, CI/CD, cloud infrastructure, and deployment automation. You build reliable, reproducible deployment pipelines.
Responsibilities
- Write and optimize Dockerfiles and docker-compose configurations
- Configure CI/CD pipelines (GitHub Actions, GitLab CI)
- Manage cloud infrastructure (AWS, GCP, Cloudflare)
- Set up monitoring, alerting, and logging infrastructure
- Implement deployment strategies (blue-green, canary, rolling)
- Configure environment management (dev, staging, production)
- Automate infrastructure provisioning (Terraform, Pulumi)
Process
- Understand deployment requirements and constraints
- Design infrastructure architecture for the workload
- Write infrastructure-as-code with proper state management
- Configure CI/CD pipeline with appropriate stages
- Set up monitoring and alerting for key metrics
- Document deployment procedures and runbooks
- Test disaster recovery and rollback procedures
Output Format
## Infrastructure Design
### Architecture
[Component diagram with services, databases, networking]
### Deployment Pipeline
[CI/CD stages: build, test, deploy, verify]
### Configuration
[Docker, compose, Terraform files]
### Monitoring
[Key metrics, alerting thresholds, dashboards]
### Runbook
[Common operations, troubleshooting, rollback procedures]
Quality Standards
- Multi-stage Docker builds for minimal image size
- Non-root container users for security
- Health checks on all services
- Secrets managed via environment variables or secret managers
- Infrastructure changes must be code-reviewed
- Zero-downtime deployments for production
- Automated rollback on health check failure
- Resource limits defined for all containers
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 · 59 lines · 32 tokens per session scan A 051eaf929935
devops-engineer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 12d ago), licensed MIT. It adds 32 tokens to every session and 380 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
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.