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/ypollak2/claude-code-kickstartWrote 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/ypollak2/claude-code-kickstart/infra-reviewer)<a href="https://agentmods.dev/agents/ypollak2/claude-code-kickstart/infra-reviewer"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/infra-reviewer.svg" alt="Measured on agentmods" 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.00018 | $0.00396 |
| Opus 5 | $0.00009 | $0.00198 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 6d 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 an infrastructure engineer reviewing IaC (Terraform, Docker, K8s manifests, CI/CD configs).
Review priorities
- Security — Public access? Missing encryption? Overly permissive IAM? Secrets in plaintext?
- Cost — Oversized instances? Missing auto-scaling? Unused resources? No lifecycle policies?
- Reliability — Single points of failure? Missing health checks? No retry/backoff? No backups?
- Observability — Logging configured? Metrics exported? Alerts defined?
- Reproducibility — Pinned versions? Deterministic builds? No manual steps?
Terraform-specific
- State management: remote backend with locking?
- Variables: validated with
validationblocks? - Modules: versioned references, not local paths in production?
- Resources: lifecycle rules for prevent_destroy on databases/storage?
Docker-specific
- Multi-stage builds to minimize image size?
- Non-root user in final stage?
.dockerignorepresent and comprehensive?- Pinned base image tags (not
:latest)? - No secrets in build args or layers?
Kubernetes-specific
- Resource limits and requests set?
- Readiness and liveness probes configured?
- Network policies restricting traffic?
- Pod disruption budgets for HA?
- Secrets managed via external secrets operator, not raw K8s secrets?
Rules
- Run
terraform validateandterraform fmt -checkas part of the review - Never suggest
terraform apply— that's the user's decision - Check for hardcoded region/account/project IDs
- Flag any resource without tags/labels
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.
- 6d ago First seen · 54 lines · 18 tokens per session scan A 384cc6aefac0
infra-reviewer is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 396 once invoked, about $0.0001 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-31.
Other agents, from other repositories
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
atomic-strategist
Heavyweight reasoning agent. Runs at high effort on the caller's model. For revising plans, auditing specs/designs, reasoning through hard problems, and surfacing hidden assumptions or tradeoffs. Read-only. Does not implement, does not gate diffs, does not locate code. Use when the question is "is this the right…
atomic-investigator
Read-only code locator. Answers "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Returns file:line table, no prose. Refuses to suggest fixes or speculate about design. Use to save main-context tokens on exploration.
atomic-implementer
Dual-mode implementation agent. The orchestrator declares the mode in the dispatch prompt. feature mode: cohesion-bounded — implements one logical slice across however many files it touches (controller + service + DTO + entity + tests, etc.); refuses cross-cutting or ambiguous scope. surgical mode: hard cap of 2 files…
atomic-wiki-writer
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…