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.
git 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/agents/realgarit/fable-baton/executor)<a href="https://agentmods.dev/agents/realgarit/fable-baton/executor"><img src="https://agentmods.dev/badge/agents/realgarit/fable-baton/executor/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/agents/realgarit/fable-baton/executor"><img src="https://agentmods.dev/badge/agents/realgarit/fable-baton/executor.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.00050 | $0.00323 |
| Opus 5.5 | $0.00020 | $0.00129 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago First seen · 30 lines · 50 tokens per session scan A 8813601ebf43
executor is an agent published in the GitHub repository realgarit/fable-baton (29 stars, last pushed 15d ago), licensed MIT. It adds 50 tokens to every session and 323 once invoked, about $0.0002 per session on Opus 5.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
react-expert
Use this agent when you need expert React development with focus on React 19+ features, performance optimization, and modern frontend architecture. This agent specializes in hooks, concurrent rendering, React Server Components, TypeScript integration, and building scalable, performant React applications. Examples…
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
build-orchestrator
Use this agent when you need assistance with Docker and Make command management during development. This includes analyzing Dockerfiles for optimization opportunities, managing container lifecycles, handling volumes and data persistence, monitoring logs, and determining when rebuilds are necessary versus simple…
model-curator
Use this agent when the project model file has grown beyond a few thousand characters, or when /presence-curate is invoked. Compresses /.claude/presence/projects/ /model.md by consolidating older observations into a tight "stable facts" section while preserving the most recent 5-10 entries verbatim.
critic
Adversarial verifier. Use PROACTIVELY before claiming a nontrivial change is done, fixed, or passing — give it the claim plus the relevant diff/paths and it attempts to refute the claim with evidence.
business-lead
Business team lead. Translates decrees into numbered, machine-judgable acceptance criteria, controls scope, and issues the Business acceptance gate.