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/chafoo/anchoredWrote 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/plugins/chafoo/anchored/plugin)<a href="https://agentmods.dev/plugins/chafoo/anchored/plugin"><img src="https://agentmods.dev/badge/plugins/chafoo/anchored/plugin/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/plugins/chafoo/anchored/plugin"><img src="https://agentmods.dev/badge/plugins/chafoo/anchored/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
a 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
{
"name": "a",
"description": "Verification gate for AI work — one run file, one independent validator, evidence-gated close. CLI-only transport via the `anchored` binary over Bash, no MCP. Slash commands: /a:run /a:setup.",
"version": "0.8.0",
"author": {
"name": "chafoo"
},
"homepage": "https://github.com/chafoo/anchored",
"repository": "https://github.com/chafoo/anchored",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 395 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 12 lines scan A af2b8f64b479
a is a plugin published in the GitHub repository chafoo/anchored (3 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
spec-flow
Ships a feature only when a test that actually ran proves every requirement in its spec. Free-text requirement -> spec (you sign it off) -> plan -> review -> implement per milestone, gated by a lint/test/spec-trace loop that runs outside the model. For Node projects; your repo declares its test and lint commands in…
forge-master
Agentic loop-engineering for complex tasks. PRD -> tagged phase plan -> autonomous TDD execution loop with deterministic escalation, command-based verification, and disk-backed state that survives compaction.
lsa
Living Spec Architecture — a technology-agnostic spec layer that authors a grounded spec and verifies it before and after an external implementer builds it. LSA is NOT the implementer: any coding agent (Claude Code, Cursor) or human writes the code. Skills: discover (extract intent + gather codebase facts; the…
sl
A five-team agent organization with enforced verification: hooks that block unverified test claims and fabricated imports, ship gates bound to content hashes, and an evidence ledger. Plain register by default; the lore is an optional overlay.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
bullpen
The senior dev, unbundled. A cast of opinionated skills that make an AI agent push back on bad ideas, verify before it claims done, attack its own code, and finish like a senior engineer.