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/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/devops-engineer)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/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/ihatesea69/kiro-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/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.00032 | $0.00380 |
| Opus 5.5 | $0.00013 | $0.00152 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 59 lines · 32 tokens per session scan A 051eaf929935
devops-engineer is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 380 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
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
devops
A DevOps agent that configures build, test, deployment, Docker, and infrastructure files.
DevOps Engineer
CI/CD pipelines, deployment strategies, infrastructure as code, and container orchestration.
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.
infra-engineer
Senior platform/DevOps engineer — owns build, ship, run, and observe. Covers Docker/compose, CI/CD (GitHub Actions), deploy targets (Vercel/Render/Fly/AWS), env + config management + 12-factor, observability (structured logs, metrics, tracing, error tracking), health checks, scaling + cost, IaC, rollback/ blue-green…
devops-automator
DevOps engineer for Terraform/CDK, CI/CD, containers, and observability. Use PROACTIVELY when writing infrastructure code; /setup-deploy and /land-and-deploy own this repo's deploy pipeline.