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 skills add Pierry/harness-kit --skill devopsgit clone --depth 1 https://github.com/Pierry/harness-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/skills/pierry/harness-kit/devops)<a href="https://agentmods.dev/skills/pierry/harness-kit/devops"><img src="https://agentmods.dev/badge/skills/pierry/harness-kit/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/skills/pierry/harness-kit/devops"><img src="https://agentmods.dev/badge/skills/pierry/harness-kit/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.00035 | $0.00416 |
| Opus 5.5 | $0.00014 | $0.00166 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
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 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
DevOps conventions, team default.
Project override: if {repo}/.claude/conventions/devops.md exists, overrides any rule here. See guides/conventions-override.md.
Defaults
CI/CD:
- GitHub Actions for most repos. Workflows in
.github/workflows/. - Reusable workflows when steps repeat across repos.
- Secrets via GitHub Secrets, never inline.
- Pin actions to commit SHA, not branch.
Containers:
- Multi-stage Dockerfile. Slim base images (alpine, distroless).
- Non-root user in production stage.
.dockerignoremirrors.gitignoreessentials plus build artifacts.
Infra-as-code:
- Terraform for infra. State in remote backend (S3, etc).
- Modules in
terraform/modules/. Stacks interraform/stacks/. - Variables via
terraform.tfvars, never hardcoded.
Observability:
- Grafana dashboards JSON in repo when applicable.
- Alerts as code (Prometheus rules, Datadog monitors).
- Log structure: JSON, with
trace_id,service,level,msg.
Secrets:
- Never commit secrets. Use secret manager.
- Pre-commit hook to scan for accidental secrets.
Before writing code
Read at least 3 similar workflows or terraform modules in repo. Confirm:
- runner type (ubuntu-latest, self-hosted)
- secret naming convention
- environments (dev, staging, prod)
- approval gates for prod
Forbidden in PR
- inline secrets
- actions pinned to
@mainor@latest - terraform without state backend
- Dockerfile running as root in prod
- alerts without runbook links
Mark gaps
# TBD - verify with devops lead: {what is missing}
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 · 35 tokens per session scan A 698a0b5d52b6
devops is a skill published in the GitHub repository Pierry/harness-kit (4 stars, last pushed 16d ago), licensed MIT. It adds 35 tokens to every session and 416 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 skills, from other repositories
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
cloudflare-ops
Cloudflare Workers + Wrangler edge ops: runtime, bindings, local dev, secrets, deploy/CI, Pages-vs-Workers. Triggers on: cloudflare workers, wrangler, wrangler deploy, wrangler.toml, KV, D1, R2, durable objects, queues, vectorize, compatibilitydate, edge functions, illegal invocation, waitUntil, caches API, smart…
terraform-ops
Terraform and OpenTofu infrastructure-as-code operations - project layout, state management, module design, plan/apply safety, CI/CD pipelines, and secrets. Use for: terraform, opentofu, infrastructure as code, IaC, tfstate, terraform state, terraform module, remote backend, terraform plan, terraform apply, foreach…
openbao-dynamic-aws-creds
Replace a static AWS access key with short-lived STS creds minted by OpenBao's AWS engine via a credentialprocess wrapper. Covers architecture, bring-up, verification, upgrade caution. Use for a static key or credentialprocess diagnosis.
terraform-iac
Terraform infrastructure as code with state management, modules, workspaces, lifecycle rules, and CI/CD patterns.
infrastructure-planning
Plan and document the required software, infrastructure, and logistics for a Paperclip company — domains, GitHub, Docker Hub, Kubernetes, Slack, Google Workspace, Stripe, shipping providers, and CI/CD pipelines. Use when setting up infrastructure for a new company or auditing what an existing company needs.