Installs into your user-level AI tool configuration; your repository only gets an agents/overrides/ folder for your own changes. Works with 20 AI coding tools.
Agent Config — teach your AI coding agents to check their work before they say done
Install once. Your AI coding tools are told to plan, test and verify before they say done; on Claude Code a turn that changed files without checking them can be stopped.
npx -y @event4u/agent-config init
Free and MIT-licensed. Node 22.6 or newer on macOS, Linux or WSL2. Costs more tokens: 7.8× a run with no rules on Claude Haiku as installed, 2.9× with only the core rules. What it costs →
On a desktop this opens a browser wizard: pick your role and your tools, click Finish. Nothing is written before you do.
Try it in 30 seconds
Not ready to install anything? Drop one read-only checker into your repo and ask it whether your branch is really done:
mkdir -p .claude/agents
curl -fsSL https://raw.githubusercontent.com/event4u-app/agent-config/main/docs/wedge/production-validator/production-validator.md \
-o .claude/agents/production-validator.md
# then in Claude Code: @production-validator check this branch is actually done
production-validator reads the code that would ship, hunts mocks and placeholders on that path and asks for proof that it ran. It changes nothing. What it checks →
What changes
Before. You ask your agent to add a CSV export. It writes a handler that
returns a hard-coded placeholder, the existing tests stay green and it replies
"Done — export implemented." Nothing ever ran the new code.
After. In Claude Code you ask @production-validator whether the branch is
really done. It reads the code that would ship, finds the placeholder and
answers NOT READY with the exact file and line. On a branch that is really
finished it answers READY and reports nothing. We tested this on two cases:
one with a placeholder left in, one finished.
On Claude Code the package can also refuse to let a turn end on "done" when the
agent changed files and ran nothing to check them. On every other tool that is
an instruction the agent is asked to follow, not a block.
What your agent is asked to do
| Default behavior | With agent-config |
|---|
| Guess and edit blindly | Analyze code before changing it |
| Drift from project conventions | Follow detected stack conventions |
| Skip or invent tests | Write tests in the project's framework |
| Generic commit messages | Conventional Commits with scope + ticket links |
| Skip quality checks | Run the project's quality pipeline and fix reported errors |
| Open PRs without context | Structured PR descriptions from Jira / Linear / GitHub |
| Claim "done" without proof | Verify with real execution before claiming done |
It changes what the agent is told to do, not how smart the model is. Re-measured in November 2026 after a scorer repair, the full install's discipline gain on Claude Haiku was not significant and Claude Sonnet showed no gain; only the small core rule set kept a significant gain on Haiku. We publish results like that one instead of hiding them. The whole story →
This is the beginning of the README. Read the rest at the original. Read the full README ↗
