Anti Hall
Install always-on verify-first guards so Claude Code stops inventing APIs, sloppy git, and runaway coordinator commands.
Overview
anti-hall is a plugin marketplace for the Ship phase that enforces verify-first, anti-hallucination guards and session discipline in Claude Code.
What is this marketplace?
- 1-plugin marketplace: anti-hall verify-first Iron-Law protocol on SessionStart with re-injection after compaction
- Always-on api-guard, git-guard, command-guard, swarm-guard, speculation guards, and task-guard with user override
- SCOPE & FIDELITY discipline: simplest sufficient solution, confirm before expanding scope, match rigor to blast radius
- Per-turn nudge keeps verification salient across long sessions
- Optional mcp-reaper companion (macOS/Linux) to terminate orphaned MCP processes only
- 1 plugin in marketplace (anti-hall)
- SessionStart + post-compaction re-injection of full protocol
- 6+ always-on guard families with user-override escape hatch
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders lose hours when coding agents invent APIs, over-scope fixes, and push risky git or GitHub actions without a persistent verify-first ritual.
Who is it for?
Indie developers running long Claude Code sessions who want default-on quality rails without replacing their existing stack.
Skip if: Teams that forbid session hooks, need zero guard friction, or do not use Claude Code’s marketplace plugin model.
What do I get? / Deliverables
After you add the marketplace, SessionStart and always-on guards steer every turn toward evidence-checked code, safer VCS habits, and accountable task progress.
- Session-injected Iron-Law and SCOPE & FIDELITY protocol
- Always-on coordinator and git/api/task guards
- Optional MCP process cleanup via mcp-reaper
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is Ship because the marketplace’s core value is quality gates and review discipline before changes escape to production. Review is where rationalization tables, scope fidelity, and output-presentation rules matter most for solo builders auditing agent output.
How it compares
Always-on session guards and discipline protocol, not a one-off lint skill or generic MCP server.
Common Questions / FAQ
Who is Anti Hall for?
It is for solo and indie builders using Claude Code who want verify-first habits and hard guards against fabricated APIs and reckless git automation.
When should I use Anti Hall?
Use it whenever agent-assisted coding is in your critical path—especially before reviews, commits, and multi-step coordinator workflows.
How do I add Anti Hall to my agent?
Register the talas9/Anti Hall Claude Code marketplace in your Claude Code settings, enable the Anti Hall plugin, and keep overrides only for intentional exceptions.