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 AlexK020908/infra-designer/plugin install infra-designerWrote 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/commands/alexk020908/infra-designer/audit)<a href="https://agentmods.dev/commands/alexk020908/infra-designer/audit"><img src="https://agentmods.dev/badge/commands/alexk020908/infra-designer/audit/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/commands/alexk020908/infra-designer/audit"><img src="https://agentmods.dev/badge/commands/alexk020908/infra-designer/audit.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.00013 | $0.00408 |
| Opus 5 | $0.00006 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
audit 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 8d 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
Audit infrastructure
Check that the live infrastructure still matches the spec, and report any drift using the user's own component names.
Spec path: $ARGUMENTS. If omitted, look under infra/ in the current working directory
for a <project-name>/spec.json; if there are several projects, ask the user which one.
All paths are relative to the user's cwd, never ${CLAUDE_PLUGIN_ROOT}. Below,
<dir> is the folder the spec lives in (e.g. infra/todo-app).
1. Capture live state
From the Terraform working directory:
cd <dir>/terraform
terraform show -json > ../state.json
terraform show -json is the source of truth for what's actually deployed. If there's
no Terraform state (infra wasn't deployed via /deploy), tell the user — auditing
unmanaged infra is a later capability.
2. Run the checks
python ${CLAUDE_PLUGIN_ROOT}/engine/audit.py <dir>/spec.json <dir>/state.json
Each component ships an audit.yaml of declarative checks; the runner evaluates them
against the live state. Exit code is non-zero if any check fails (useful in CI).
3. Report and offer fixes
- Summarize by node: what passed, what drifted, severity.
- For each drift, explain what changed and why it matters (read the component's
SKILL.mdif the user asks why a setting matters). - Offer to reconcile: update
<dir>/spec.jsonto match reality (accept the change) or re-run/deployto push the spec back onto the infra (revert the drift). Let the user choose per item — don't auto-apply.
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.
- 8d ago First seen · 46 lines · 13 tokens per session scan A aa51cfb4291b
audit is a command published in the GitHub repository AlexK020908/infra-designer (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 408 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 commands, from other repositories
k8s-manifest
Generate production-ready Kubernetes manifests for the current application.
setup-lambda
Configure and deploy an AWS Lambda function with proper settings.
uninstall
Uninstall filetree from this repo — un-wires CLAUDE.md/AGENTS.md, removes generated artifacts (confirmed per item), tears down self-only mode if enabled.
rclone_sync
Make source and dest identical, modifying destination only.
rclone_serve_s3
Serve remote:path over s3.
checklist
Generate a custom checklist for the current feature based on user requirements.