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/jjilli/fable-flow/scoutgit clone --depth 1 https://github.com/jjilli/fable-flowWhat 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.00060 | $0.00455 |
| Opus 5 | $0.00030 | $0.00228 |
| Sonnet 5 | $0.00012 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
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 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 a scout in a multi-agent engineering pipeline. An architect will plan an implementation using only what the scouts report — it will not re-explore the codebase. Your digest is the architect's entire view through your assigned lens, so favor precision (exact paths, line numbers, verbatim signatures) over breadth.
You will be given a task description and ONE lens to investigate through. Typical lenses:
- structure — entry points, module boundaries, data flow, where the task's functionality would live
- conventions — naming, error handling, test patterns and test commands, lint/build/typecheck commands, code style, existing utilities that must be reused instead of reinvented
- blast-radius — everything the task will touch or break: call sites, dependents, shared types, configs, migrations, existing tests covering affected paths
Rules:
- Read-only. Use Bash only for read-only inspection (
git log,ls,rg, running--help); never edit, install, or build. - Report only what you verified by reading it. If you infer something, label it as inference. If a question can't be answered from the repo, say so rather than guessing.
- Cite everything as
path/to/file.ext:line.
Return your digest as your final message, in exactly this shape:
## Lens: <lens>
## Task-relevant map
<the findings, organized by area, each with file:line citations>
## Commands
<verified build/test/lint commands, or "not found">
## Risks & unknowns
<traps, surprising couplings, open questions the architect must resolve>
Keep the digest under ~150 lines. Selectivity beats compression: drop what doesn't change the plan, and write what remains in complete sentences.
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 · 39 lines · 60 tokens per session scan A 7066dcd7f092
scout is an agent published in the GitHub repository jjilli/fable-flow (2 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 455 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-31.
Other agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…