Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add realgarit/fable-baton --skill baton-setupgit clone --depth 1 https://github.com/realgarit/fable-batonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/realgarit/fable-baton/baton-setup)<a href="https://agentmods.dev/skills/realgarit/fable-baton/baton-setup"><img src="https://agentmods.dev/badge/skills/realgarit/fable-baton/baton-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/realgarit/fable-baton/baton-setup"><img src="https://agentmods.dev/badge/skills/realgarit/fable-baton/baton-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00069 | $0.00696 |
| Opus 5.5 | $0.00028 | $0.00278 |
| Sonnet 5.5 | $0.00014 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade B, and why
baton-setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
description: One-time setup and health check for fable-baton. Use when the user asks to set up, configure, verify, or troubleshoot fable-baton - sets the default model to "best" (Fable 5 with Opus fallback) in ~/.claude/ How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
baton-setup
One-time setup for fable-baton. Run each step in order. Never rewrite ~/.claude/settings.json wholesale - edit only the named keys and preserve everything else.
Step 1 - Read current state
- Read
~/.claude/settings.json(if missing, you will create a minimal one). - Check
echo "$CLAUDE_CODE_SUBAGENT_MODEL". If set, warn the user: this variable silently overrides every agent'smodelfrontmatter and defeats the tiering. Recommend unsetting it, but do not unset it yourself without approval.
Step 2 - Propose changes and get approval
Show the user exactly what you will change before writing anything:
| Key | Rule |
|---|---|
model |
If absent → set "best". If present with a different value → ask: keep theirs, or switch to "best"? (best resolves to Fable 5 when the account has access, otherwise the latest Opus.) If already "best" → no change. |
fallbackModel |
If absent → add ["opus", "sonnet"] (covers overload/unavailability). If present → leave it. |
availableModels |
Only if the key already exists (it is an allowlist): ensure it contains "opus", "sonnet", "haiku", and the chosen main-model value. If absent → do not add it. |
Back up the file first: copy it to ~/.claude/settings.json.baton-backup-<YYYYMMDD-HHMMSS> (skip if the file didn't exist).
Step 3 - Apply and validate
Apply the approved edits, then validate: jq empty ~/.claude/settings.json must exit 0 (or parse the JSON yourself if jq is unavailable).
If Claude Code rejects the best alias at startup (older versions), fall back to "opus" and suggest updating Claude Code.
Step 4 - Verify the install
- Confirm the four agents are available: scout, executor, architect, verifier (ask "which subagent types are available?" or check the Agent tool's list).
- Confirm the orchestration policy is present in context (it is injected at session start; in a session started before install it won't be - that's expected).
- Tell the user to restart their Claude Code session: agents and the model setting load at session start.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 47 lines · 69 tokens per session scan B cb2d1af85cfd
baton-setup is a skill published in the GitHub repository realgarit/fable-baton (29 stars, last pushed 22d ago), licensed MIT. It adds 69 tokens to every session and 696 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
apex-review
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
apex-recon
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
apex-takeover
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
fable-voice
Use when about to write your final reply, a summary, PR description, commit message, or any user-facing conclusion — enforces Fable's outcome-first, prose-first communication contract.
fable-fanout
Use when a task involves 2+ independent units of work (files, modules, questions) or any broad codebase sweep — enforces Fable's delegation-first parallel orchestration.