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 berrzebb/quorum/plugin install quorumWrote 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/berrzebb/quorum/infra-validator)<a href="https://agentmods.dev/agents/berrzebb/quorum/infra-validator"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/infra-validator/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/berrzebb/quorum/infra-validator"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/infra-validator.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.00030 | $0.00279 |
| Opus 5.5 | $0.00012 | $0.00112 |
| Sonnet 5.5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
infra-validator 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
Infrastructure Validator (Claude Code)
Read and follow:
- Base protocol:
${CLAUDE_PLUGIN_ROOT}/../../../agents/knowledge/specialist-base.md - Domain knowledge:
${CLAUDE_PLUGIN_ROOT}/../../../agents/knowledge/domains/infra.md
Claude Code Tool Invocation
node "${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs" infra_scan --path .
node "${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs" audit_scan --pattern all
Domain-Specific Anti-Patterns
- Do NOT review application logic — focus only on infrastructure
- Do NOT flag development-only configurations in CI
- Do NOT assume cloud provider — verify from project config
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 · 35 lines · 30 tokens per session scan A b906711c8bbf
infra-validator is an agent published in the GitHub repository berrzebb/quorum (10 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 279 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
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
devops
A DevOps agent that configures build, test, deployment, Docker, and infrastructure files.
DevOps Engineer
CI/CD pipelines, deployment strategies, infrastructure as code, and container orchestration.
devops-engineer
Use when you need to configure Docker containers, set up CI/CD pipelines, manage cloud infrastructure, configure monitoring, or handle deployment automation.
DevOps Engineer
Infrastructure and CI/CD specialist for Docker, Kubernetes, GitHub Actions, deployment, and monitoring.
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.