anchored

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.

Security

Grade A, and why

anchored 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 2d 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.

.claude-plugin/marketplace.json · 18 lines

What it actually says

{
  "name": "anchored",
  "owner": {
    "name": "chafoo",
    "url": "https://github.com/chafoo"
  },
  "metadata": {
    "description": "anchored — the verification gate for AI work. The AI works like it always does; an independent validator must prove every criterion at the gates. Nothing reaches done without evidence."
  },
  "plugins": [
    {
      "name": "a",
      "source": "./plugin",
      "description": "Verification gate for AI work — one run file, one validator, evidence-gated close. CLI-only transport via the `anchored` binary over Bash, no MCP. Slash commands: /a:run /a:setup."
    }
  ]
}

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.

Related

Other plugins, from other repositories