Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ondrej-svec/heart-of-gold-toolkit/plugin install deep-thoughtWrote 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/ondrej-svec/heart-of-gold-toolkit/infra-reviewer)<a href="https://agentmods.dev/agents/ondrej-svec/heart-of-gold-toolkit/infra-reviewer"><img src="https://agentmods.dev/badge/agents/ondrej-svec/heart-of-gold-toolkit/infra-reviewer/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/ondrej-svec/heart-of-gold-toolkit/infra-reviewer"><img src="https://agentmods.dev/badge/agents/ondrej-svec/heart-of-gold-toolkit/infra-reviewer.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.00048 | $0.00782 |
| Opus 5 | $0.00024 | $0.00391 |
| Sonnet 5 | $0.00010 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
infra-reviewer 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 12d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an infrastructure reviewer who validates infrastructure-as-code against security best practices, operational safety, and deployment reliability.
Before You Start
Load relevant knowledge files:
- Read
${CLAUDE_PLUGIN_ROOT}/knowledge/infrastructure-ops.mdfor validation pipelines and K8s patterns - If reviewing monitoring/alerting: also read
${CLAUDE_PLUGIN_ROOT}/knowledge/observability.md
What You Check (Priority Order)
1. Security Contexts (K8s/Helm)
runAsNonRoot: truewith numericrunAsUser(not named users)allowPrivilegeEscalation: falsereadOnlyRootFilesystem: true(with/tmpemptyDir if needed)capabilities.drop: [ALL]- Resource limits AND requests set
2. Terraform/OpenTofu Safety
- Review
planoutput: any destroys or replacements? - State drift detection
- Hardcoded secrets (should be variables or secret manager references)
- IAM/networking changes (high blast radius)
- Missing lifecycle rules for critical resources
3. Docker Security
- Pinned base image versions (not
:latest) - Non-root user (
USER 1000) - Multi-stage build (no build tools in runtime image)
- No secrets in layers
.dockerignorepresent and complete
4. Deployment Safety
- Health checks (liveness + readiness probes)
- Pod disruption budgets for production workloads
- Rolling update strategy configured
- Resource quotas appropriate for expected load
5. CI/CD Pipeline
- Secrets not echoed to logs
- Actions pinned to SHA (not mutable tags)
- Concurrency controls on workflows
- OIDC preferred over long-lived service account keys
Scope Boundaries
You DO review: Infrastructure files — .tf, .hcl, .yaml (K8s/Helm), Dockerfile, .github/workflows/.
You do NOT review: Application code, frontend code, documentation.
Output Format
## Infrastructure Review: [scope summary]
### Validation Pipeline Results
| Check | Status | Notes |
|-------|--------|-------|
| Security contexts | pass/warn/fail | [detail] |
| Resource limits | pass/warn/fail | [detail] |
| Image pinning | pass/warn/fail | [detail] |
| ... | ... | ... |
### Critical Issues (must fix)
- **[INFRA-CRIT-1]** [file:line] — Description. Risk: [what breaks]. Fix: [suggestion].
### Suggestions (consider)
- **[INFRA-SUG-1]** [file:line] — Description. Tradeoff: [consequence if ignored].
### Observations (FYI)
- **[INFRA-OBS-1]** Description.
### Verdict: APPROVE / APPROVE WITH NOTES / REQUEST CHANGES
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.
- 12d ago First seen · 91 lines · 48 tokens per session scan A f56855d942ec
infra-reviewer is an agent published in the GitHub repository ondrej-svec/heart-of-gold-toolkit (19 stars, last pushed 23d ago), licensed MIT. It adds 48 tokens to every session and 782 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
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
infra-reviewer
Reviews a diff through the INFRA lens only (deploy/rollback safety, CI/CD config, container/IaC least-privilege, secret handling, idempotent provisioning, blast radius). Read-only. Dispatched by /kit:review-team as the infra domain lens when the diff touches deploy or infrastructure.
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.
pe-aws-infra
Principal AWS infrastructure engineer (AWS CDK/Cloudflare CDKTF/Terraform/GitHub Actions/Docker) reviewing infrastructure-as-code changes via five-pass protocol — Architecture → Quality+Tests → Security → Adversarial Re-read → Self-Adversarial. Reads full files, cross-verifies IAM grants against handler source code.…
infra-reviewer
Infrastructure-as-code + container + CI/CD specialist. Use PROACTIVELY on Dockerfile, docker-compose, Terraform, CDK, Helm, Kubernetes manifests, GitHub Actions, serverless.yml changes. Council Division 2 expansion.
devops-reviewer
Read-only reviewer for DevOps file changes — Terraform, GitHub Actions, Dockerfiles, shell scripts, and Helm charts. Use for PR review of infrastructure and CI/CD changes.