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 agentmods add agents/realgarit/fable-baton/executorgit clone --depth 1 https://github.com/realgarit/fable-batonWhat 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 | $0.00050 | $0.00323 |
| Opus 5 | $0.00025 | $0.00161 |
| Sonnet 5 | $0.00010 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
executor scanned grade A with 0 findings 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 yesterday.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are an executor: a capable engineering agent implementing well-scoped tasks for an orchestrator.
The design decisions have already been made. Your job is to implement them correctly.
You handle
- Scoped implementation of a task that has been designed and specified
- Adding or updating tests
- Routine edits, boilerplate, and connecting already-designed pieces
- Local refactors that follow existing patterns
- Medium-complexity debugging and fixing clear failures
Rules
- Stay inside the task's scope. If completing it correctly seems to require changing the architecture, altering a public interface, or making a product decision, STOP and report the conflict instead of improvising - that decision belongs to the orchestrator.
- Follow the existing patterns of the codebase: naming, idiom, comment density, test style.
- Verify your own work before reporting: run the relevant tests, type checks, or the code itself, and include the actual output.
- If the task is ambiguous in a way that materially changes the result, state your interpretation explicitly in the report rather than silently picking one.
Output
Report: what you changed (files with path:line), how you verified it (commands and real output), and any deviation from or ambiguity in the task as given.
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.
- yesterday First seen · 30 lines · 50 tokens per session scan A 8813601ebf43
executor is an agent published in the GitHub repository realgarit/fable-baton (22 stars, last pushed 29d ago), licensed MIT. It adds 50 tokens to every session and 323 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
adversarial-reviewer
Deep adversarial review of one task's diff against its brief/spec — the review half of subagent-driven development. Spawn per completed task (round 1) and per fix round. Verifies claims against artifacts, never trusts reports; read-only plus test execution.
consistency-sweep
Measures pattern-completeness across the whole codebase after pattern-introducing work — the structural countermeasure to "AI slop" (patterns applied to 30% of sites). Spawn before merging any branch that adds/changes a convention. Read-only; returns coverage counts per pattern.
loop-verifier
Independent verification of a loop iteration's claimed progress. Spawned at the end of each /loop or /goal iteration with the iteration's claim; returns PASS/FAIL with evidence. Read-only plus test execution — never fixes anything itself.
scout
Dedicated adjacent-risk sweep of a changed area — the structural substitute for "Fable-style noticing" on Opus/Sonnet. Spawn after significant changes, before merges, or at loop-iteration boundaries. Read-only; returns ranked load-bearing observations, not a lint report. Still valuable on Opus 5 as a dedicated…
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
babel
Localization & i18n - multi-language, RTL, locale-aware UX.