A verification gate for AI work that runs one task file and uses an independent validator to check the evidence before the work is closed.

Use its /a:run and /a:setup commands to run and configure the validation process through the command line.

It helps prevent incomplete or unsupported work from being treated as finished.

a — Plugin by chafoo

Install

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.

Claude Code

/plugin marketplace add chafoo/anchored

agentmods

npx agentmods add plugins/chafoo/anchored/plugin

Clone the repo

git clone --depth 1 https://github.com/chafoo/anchored

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

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 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.

plugin/.claude-plugin/plugin.json · 12 lines

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"
}

Changes

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 · 12 lines scan A af2b8f64b479

Subscribe to this mod's changes

a is a plugin published in the GitHub repository chafoo/anchored (3 stars, last pushed 1mo 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.

Planning agent-orchestration agentic autonomous-ai-coding claude-code-plugin developer-tools spec-driven-development

milestone-driver

Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…

kenmulford/milestone-driver · not measured

a

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

milestone-driver

constitution

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins