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.
npx agentmods add commands/mulkatz/anvil/anvil-statusgit clone --depth 1 https://github.com/mulkatz/anvilWrote 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/mulkatz/anvil/anvil-status)<a href="https://agentmods.dev/commands/mulkatz/anvil/anvil-status"><img src="https://agentmods.dev/badge/commands/mulkatz/anvil/anvil-status.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 | $0.00006 | $0.00243 |
| Opus 5 | $0.00003 | $0.00121 |
| Sonnet 5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
anvil-status 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 4d 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
Anvil Status
Check the current debate status:
-
Check if
.claude/anvil-state.local.mdexists using Bash:test -f .claude/anvil-state.local.md && echo "EXISTS" || echo "NOT_FOUND" -
If NOT_FOUND: Say "No active Anvil debate."
-
If EXISTS:
- Read
.claude/anvil-state.local.md - Report the following from the YAML frontmatter:
- Question: the
questionfield - Mode: the
modefield - Phase: the
phasefield (advocate/critic/synthesizer) - Round:
roundofmax_rounds - Research: the
researchfield (true/false) - Started: the
started_atfield
- Question: the
- Read
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.
- 4d ago First seen · 26 lines · 6 tokens per session scan A 201a9bbc9c44
anvil-status is a command published in the GitHub repository mulkatz/anvil (1 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 243 once invoked, about $0.0000 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
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
build
Guided feature development with approval gates at each phase.