I built a tiny CI tool to keep AI agent configs from drifting in my repo

If your team uses AI coding agents on real code, you've probably hit this: The rules your agents are supposed to follow — what tools they're allowed to use, who can call who, when something should escalate — live in scattered prompts, READMEs, and Notion docs. Nothing in your CI pipeline fails when reality drifts from those documents. So I made a small thing. What it does It turns the rules into YAML that lives in your repo: # .agent-ops/registry/tool-acl.yaml backend-builder:...