agent-chaperone/agent-chaperone#78 extends the hooks adapter past Claude Code, one agent at a time. Each agent that gains an adapter needs a page here, because the setup and the limits differ enough between agents that one generic page would be wrong for most of them.
For each agent, when its adapter is released:
- A guide under
/guides, or an extension of that agent's existing MCP guide where one exists, rather than a second page about the same agent.
- The configuration, copied from the tool repository's docs and checked against a real run of that agent.
- What the adapter can do on that agent before a call (deny, and ask only where the agent has it) and after one (withhold where the agent lets a hook replace a result, annotate where it only lets a hook add text), stated plainly rather than implied to match Claude Code.
- What reaches the model unscreened on that agent, and whether a hook that crashes lets the call through.
- An entry in
src/data/guides.ts, so the index, the structured data, llms.txt and the sitemap pick it up, and in the IndexNow list.
- A description between 25 and 160 characters, which the build enforces.
The page follows the release, not the pull request, so it never describes an adapter a reader cannot install yet.
agent-chaperone/agent-chaperone#78 extends the hooks adapter past Claude Code, one agent at a time. Each agent that gains an adapter needs a page here, because the setup and the limits differ enough between agents that one generic page would be wrong for most of them.
For each agent, when its adapter is released:
/guides, or an extension of that agent's existing MCP guide where one exists, rather than a second page about the same agent.src/data/guides.ts, so the index, the structured data, llms.txt and the sitemap pick it up, and in the IndexNow list.The page follows the release, not the pull request, so it never describes an adapter a reader cannot install yet.