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 agents/samibs/skillfoundry/_anvil-protocolgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/_anvil-protocol)<a href="https://agentmods.dev/agents/samibs/skillfoundry/_anvil-protocol"><img src="https://agentmods.dev/badge/agents/samibs/skillfoundry/_anvil-protocol.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.00000 | $0.02123 |
| Opus 5 | $0.00000 | $0.01061 |
| Sonnet 5 | $0.00000 | $0.00425 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
_anvil-protocol 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 yesterday.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Anvil — 7-Tier Agent-Handoff Gate Protocol (A0–A6)
Version: 1.1 Status: ACTIVE Applies To: All Agents in the Story Execution Pipeline
Purpose
The Anvil is a 7-tier validation system that runs between every agent phase in the story execution pipeline. It catches issues at the source — before they cascade through the chain and require expensive re-runs.
Core insight: LLMs generate code optimistically (forward, single-pass) but debug analytically (backwards from evidence). The Anvil forces analytical validation at every handoff point, not just at the end.
Namespace — read this first. Anvil tiers use the A-namespace (A0–A6). They are agent-handoff prompt checks. They are distinct from the CLI quality gates (T0–T7) implemented in
sf_cli/src/core/gates.tsandscripts/anvil.sh, which the deterministicsfengine runs. The two systems have the same count but different checks — e.g. Anvil A3 is Self-Adversarial Review, while CLI gate T3 is Tests. Never conflate an "A#" (Anvil) with a "T#" (CLI gate). This is the single canonical Anvil tier definition; other docs reference it rather than re-tabulating.
The 7 Anvil Tiers (A0–A6)
| Tier | Name | Type | When | What It Catches |
|---|---|---|---|---|
| A0 | Correctness Contract | Static check (no LLM, no build) | Before any agent runs | Missing tests for completed story acceptance criteria — every done_when item must have a corresponding test |
| A1 | Shell Pre-Flight | Shell script (no LLM) | Between EVERY agent handoff | Syntax errors, banned patterns, missing files, broken imports |
| A2 | Canary Smoke Test | Quick execution test | After Coder, before Tester | Fundamental breakage — module won't import, won't compile |
| A3 | Self-Adversarial Review | Coder self-critique | After Coder writes code | Coder's blind spots, untested failure modes |
| A4 | Scope Validation | Diff comparison | In Gate-Keeper validation | Scope creep, incomplete implementation |
| A4b | Traceability Test | Line-level diff analysis | In Gate-Keeper validation (after A4) | Orthogonal changes — lines that don't trace to the request (see LLM-020) |
| A5 | Contract Enforcement | API contract check | In Gate-Keeper validation | API drift, wrong signatures, missing endpoints |
| A6 | Shadow Tester | Parallel risk agent | Concurrent with Coder | Risk prioritization for Tester, early warnings |
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.
- yesterday First seen · 203 lines · 0 tokens per session scan A 0cb8f198276f
_anvil-protocol is an agent published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,123 tokens. 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-09-03.
Other agents, from other repositories
Azure Sweeper
Enterprise-grade Azure environment sweeper — WAF + CAF + Landing Zone + Org Rules + Policy + Resource Graph + Telemetry + Remediation. Run on any scope to produce a prioritised findings report with remediation code.
Blazor Reviewer
Review Blazor / Razor components for layer violations, lifecycle bugs, accessibility gaps, and Fluent UI misuse. Use for PR reviews on .razor / .razor.cs files.
Specifier
Interview the user to define what and why before any technical planning. Surfaces ambiguities as [NEEDS CLARIFICATION] markers that block hardening.
Plan Health Auditor
Read-only plan health auditor — analyzes run history, failure modes, gate-portability issues, and slice retry rates, then proposes concrete patches.
CI/CD Pipeline Reviewer
Review CI/CD pipelines for best practices: environment promotion, secrets management, rollback strategies, build caching, and deployment safety.
Multi-Tenancy Reviewer
Audit code for multi-tenancy isolation: data leakage, tenant-scoped queries, RLS, cache separation, and cross-tenant access prevention.