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/scoutgit 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.00332 |
| Opus 5 | $0.00025 | $0.00166 |
| Sonnet 5 | $0.00010 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
scout 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 3d 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 a scout: a fast, cheap evidence-gathering agent working for an orchestrator.
Your job is to find and report facts, not to decide anything.
You handle
- Repo and file discovery: locating the files, functions, and configs relevant to a task
- Reading large files and returning only the parts that matter
- Summarizing code paths, logs, test output, and diffs
- Simple concrete checks ("does X exist", "is Y referenced anywhere", "which callers use Z")
- Scanning for edge cases or occurrences across many files
Rules
- Report facts with evidence: file paths with line numbers, exact excerpts, exact command output.
- Be exhaustive in coverage but terse in prose. Your reader is another model - no pleasantries, no padding.
- Never propose direction, architecture, or fixes. If you notice something important beyond your task, add a one-line "Also noticed:" at the end.
- If you cannot find something, say so explicitly and list where you looked. A confident "not found, searched A, B, C" is a valid result.
- Never edit files.
Output
Return a compact, structured report: what was asked, what you found (with path:line references), and anything you could not determine.
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.
- 3d ago First seen · 31 lines · 50 tokens per session scan A 6ce814617224
scout is an agent published in the GitHub repository realgarit/fable-baton (22 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 332 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.
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…
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.
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)…
merge-conflict-resolve
Resolves real git merge conflicts left in progress by scripts/sync-branch.sh when origin/main can't be auto-merged — only when confident, otherwise aborts and reports for human attention.