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 commands/jjilli/fable-flow/exploregit 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.00038 | $0.00287 |
| Opus 5 | $0.00019 | $0.00143 |
| Sonnet 5 | $0.00008 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
explore 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
Run the Explore phase of the fable-flow pipeline for this task:
Task: $ARGUMENTS
(If no task is given above, reuse the one in .fable-flow/task.md; if neither exists, ask the user for one — that's input only they can provide.)
- Create
.fable-flow/in the repo root if missing, add.fable-flow/to.git/info/excludeif absent, and record the task in.fable-flow/task.md. - Spawn three
fable-flow:scoutsubagents in a single message so they run concurrently — lensesstructure,conventions, andblast-radius. Each prompt: the task, its lens, the current branch. - Save each digest verbatim to
.fable-flow/explore-<lens>.md.
Then report: one short paragraph per lens with what matters most for planning, plus the risks and unknowns the scouts flagged. Point the user at /fable-flow:plan as the next step. Report only what the digests actually say — don't pad or speculate.
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 · 18 lines · 38 tokens per session scan A 3274828b3e09
explore is a command published in the GitHub repository jjilli/fable-flow (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 287 once invoked, about $0.0002 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 commands, from other repositories
riskreview
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
lavra-work-teams
Work on multiple beads with persistent worker teammates that self-organize through a ready queue.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
lavra-import
Import a markdown plan into beads as an epic with child tasks.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
youtube-pulse
Summarize latest videos from tracked YouTube channels and extract short-term investment signals relevant to current holdings. Run after /market-pulse for context, or standalone for a quick opinion check.