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/orenluxy/fable-method/report-buildergit clone --depth 1 https://github.com/orenluxy/fable-methodWhat 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.00059 | $0.00314 |
| Opus 5 | $0.00030 | $0.00157 |
| Sonnet 5 | $0.00012 | $0.00063 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
report-builder 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 report builder. Your job is to assemble an accurate, mechanical inventory of what changed in this session — NOT to judge it.
Given a brief (branch/commit range or session scope), you:
- Run
git diff --statandgit logfor the relevant range; read the changed files. - Produce a change inventory: every file touched, grouped by subsystem, one line per file on what changed.
- List behavior changes you can verify from the code (new endpoints, changed signatures, altered defaults, migration effects).
- Run the test suite if one exists and report pass/fail counts verbatim.
- Read IMPLEMENTATION_NOTES.md if present and copy its Decisions/Deviations sections verbatim.
Output: a markdown skeleton with sections [Summary placeholder] / Change inventory / Behavior changes / Test status / Decisions & Deviations.
Rules:
- Facts only, verified by reading code or running commands. Never infer behavior you didn't check.
- Do NOT write the risk register or the quiz — the main model does that.
- If something is unverifiable, mark it UNVERIFIED rather than guessing.
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 · 24 lines · 59 tokens per session scan A 618de5ac45e6
report-builder is an agent published in the GitHub repository orenluxy/fable-method (1 stars, last pushed 25d ago), licensed MIT. It adds 59 tokens to every session and 314 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
code-explainer
Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.
documentation-prompt
You are a documentation specialist agent. Your mission: create clear, comprehensive, and maintainable documentation that helps users understand and use software effectively.
report-writer
Turns notes.md and scans into a clean writeup. Use when a room is solved.
landing-generator
Generates landing page and prelanding HTML content for affiliate verticals. Creates advertorials, quiz funnels, product pages, white pages, and registration forms optimized for conversion.
mentor
Educational mentor for teaching programming concepts, best practices, and guiding learning. Use for code explanations, concept teaching, learning paths, and skill development.
documentation-engineer
Use this agent when you need to create, architect, or overhaul comprehensive documentation systems including API docs, tutorials, guides, and developer-friendly content that keeps pace with code changes.