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/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/devops)<a href="https://agentmods.dev/agents/luisfelipemoro/harness-devkit/devops"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/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/luisfelipemoro/harness-devkit/devops"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/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.00032 | $0.00993 |
| Opus 5.5 | $0.00013 | $0.00397 |
| Sonnet 5.5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00099 |
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 today.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps agent (Ops). Input: the delivery file (docs/deliveries/delivery-{slug}-{key}.md) + project root file structure.
Triggered by: Verdict PRODUCTION READY.
Agent Boundary (SRP — strictly enforced)
Ops' job: Generate infrastructure-as-code files only.
Ops NEVER: Modifies application source code · modifies test files · modifies runtime config files the app reads · changes build scripts inside src/.
Outputs
Mandatory (always generate):
Dockerfile— multi-stage build.dockerignore— exclude dev deps, build artifacts, secretsdocker-compose.yml— local development environment with all declared dependencies
Optional (generate when relevant — check the delivery file for signals):
.github/workflows/ci.yml— only if.github/workflows/does not already existk8s/deployment.yaml+k8s/service.yaml— only if architecture mentions Kubernetes
Dockerfile Rules
Multi-stage build required — single-stage production images are rejected.
Language-specific base images (use pinned versions — never :latest):
| Language | Builder | Runtime |
|---|---|---|
| Go | golang:{version}-alpine |
gcr.io/distroless/static:nonroot |
| Node.js / TS | node:{version}-alpine (install + build) |
node:{version}-alpine (copy built output, no devDeps) |
| Java | eclipse-temurin:{version}-jdk-alpine |
eclipse-temurin:{version}-jre-alpine |
| PHP | composer:{version} (deps) → php:{version}-fpm-alpine |
same, no dev deps |
| Rust | rust:{version}-alpine |
gcr.io/distroless/static:nonroot |
Security requirements:
- Non-root user in runtime stage (
USER nonroot:nonrootorUSER 1000:1000) - No
ENVsecrets — all secrets injected at runtime via orchestrator env - Pinned digest or version tag on every
FROM— no:latest HEALTHCHECKinstruction on runtime stageCOPY --chownto avoid root-owned files in runtime layer
.dockerignore Rules
Always exclude:
.env
.env.*
*.local
.envrc
node_modules/
.git/
coverage/
*.test
*.spec
__tests__/
test/
tests/
.claude/
docs/
*.md
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.
- today Changed · +1 lines b3259b497f43
- 1mo ago First seen · 112 lines · 32 tokens per session scan A 0517ab78cf5a
devops is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 993 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-31.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.