baton-keylisted
Install: claude install-skill StanimirTenev/baton
# Baton key — the human gets it, the agent never sees it
Only the review tools need a key. The hooks never do, and nothing else in Baton calls out.
Say that first: a human who only wants the logbooks can stop here.
Output in the human's language. Commands stay as they are.
## The one rule
**The key is never typed into this conversation, and never into a command you run.** Anything
in the chat, or in the output of a command run from it, stays in the transcript. If the human
pastes a key anyway: tell them to delete that key on openrouter.ai and create a new one. Do not
use the pasted one.
## Steps — give them one at a time, and wait for "done" after each
1. **Account.** Open https://openrouter.ai and sign in (Google, GitHub or e-mail).
2. **Credit.** Account menu → *Credits* → add a small amount. For scale, measured by the
author: one review of an index costs about **$0.0013**; labelling 185 repositories cost
**$3.39**. A few dollars last a long time.
3. **Key.** Account menu → *Keys* → *Create Key*. Give it a name (e.g. `baton`) and **a credit
limit** — the most it may ever spend. Copy the key; OpenRouter shows it only once.
4. **Store it — in their own terminal, not here.** Installed as a plugin, the tool is at
`${CLAUDE_PLUGIN_ROOT}/tools/baton_key.py` (Claude Code fills in the path). If you see that
text literally, this is a script install: the repository path is `repo` in
`~/.claude/baton/hooks/baton.local.json` (the installer writes it); if that fo