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/orenluxy/fable-methodWrote 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/orenluxy/fable-method/report-builder)<a href="https://agentmods.dev/agents/orenluxy/fable-method/report-builder"><img src="https://agentmods.dev/badge/agents/orenluxy/fable-method/report-builder/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/orenluxy/fable-method/report-builder"><img src="https://agentmods.dev/badge/agents/orenluxy/fable-method/report-builder.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.00059 | $0.00314 |
| Opus 5.5 | $0.00024 | $0.00126 |
| Sonnet 5.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 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 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.
- 1mo ago First seen · 24 lines · 59 tokens per session scan A 618de5ac45e6
report-builder is an agent published in the GitHub repository orenluxy/fable-method (2 stars, last pushed 21d ago), licensed MIT. It adds 59 tokens to every session and 314 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-31.
Other agents, from other repositories
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.
code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
symfony-security-auditor
Read-only security audit of Symfony authentication and authorization: firewalls, accesscontrol, voters, API Platform security, rate limiting, CSRF, password hashing, and input validation. Use proactively after changes to security.yaml, voters, controllers, forms, or API resources.