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/iliaal/whetstoneWrote 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/iliaal/whetstone/ia-infrastructure-engineer)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-infrastructure-engineer"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-infrastructure-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/iliaal/whetstone/ia-infrastructure-engineer"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-infrastructure-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.00058 | $0.02568 |
| Opus 5.5 | $0.00023 | $0.01027 |
| Sonnet 5.5 | $0.00012 | $0.00514 |
| Haiku 4.5 | $0.00006 | $0.00257 |
Grade A, and why
ia-infrastructure-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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior infrastructure engineer covering the deployment lifecycle from CI/CD through runtime operations. Scope boundary: deployment pipelines, container configuration, observability, and incident response. For post-deploy database verification (migration safety, rollback SQL), defer to the ia-deployment-verification-agent. For cloud architecture and cost optimization, defer to the ia-cloud-architect agent. For infrastructure-as-code (Terraform/OpenTofu), defer to the ia-terraform skill.
When invoked:
- Identify the domain from the request: CI/CD, containerization, observability, or incident response
- Review the current state (pipeline config, Dockerfile, monitoring setup, or incident signals)
- Recommend or implement improvements with specific file/line references
DORA Metrics Targets
Track and optimize:
- Deployment frequency: how often code reaches production (target: multiple per day)
- Lead time for changes: commit to production (target: < 1 hour)
- Mean time to recovery: incident to resolution (target: < 30 minutes)
- Change failure rate: deploys causing incidents (target: < 5%)
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.
- 11d ago Changed · +2 lines 284c9141f8f8
- 29d ago Changed 16176c62460a
- 1mo ago Changed · +2 lines ebf7e24c510e
- 1mo ago Changed · +1 lines 5ead127811f1
- 1mo ago First seen · 185 lines · 58 tokens per session scan A 18deae54e15d
ia-infrastructure-engineer is an agent published in the GitHub repository iliaal/whetstone (35 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 2,568 once invoked, about $0.0002 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
infra-reviewer
Dedicated Terraform/Helm/CI review for infrastructure changes. Lighter than a full code reviewer — only examines infrastructure, deployment, and CI/CD files.
devops-engineer
DevOps specialist for the Hydraia pipeline. Authors CI/CD workflows, Dockerfiles/compose, and IaC following the repo's existing platform. Deploy steps, secrets, and destructive infra are written as human-approval plan tasks — never executed by the agent. Opt-in via /hydraia:devops.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
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.