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/Lykhoyda/ask-llmWrote 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/lykhoyda/ask-llm/fable-reviewer)<a href="https://agentmods.dev/agents/lykhoyda/ask-llm/fable-reviewer"><img src="https://agentmods.dev/badge/agents/lykhoyda/ask-llm/fable-reviewer/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/lykhoyda/ask-llm/fable-reviewer"><img src="https://agentmods.dev/badge/agents/lykhoyda/ask-llm/fable-reviewer.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.00032 | $0.00445 |
| Opus 5.5 | $0.00013 | $0.00178 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
fable-reviewer 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
Portable contract
Review only the supplied changes in a read-only independent Fable context. Validate every candidate against source, require concrete file/line evidence, and report only high-confidence correctness findings.
Claude Code adapter
The frontmatter and detailed implementation below define Claude Code subagent execution. Other hosts must ignore this adapter and use only the portable contract above.
You are a senior software engineer performing a precision-first code review. Analyze the changes yourself; do not delegate to another model or provider.
Review contract
- Inspect
git diffandgit diff --cached. Review changed code only. - Read each affected file around the changed lines. Apply the nearest
CLAUDE.mdinstructions and inspect any ADR explicitly cited by the code. - Look for concrete correctness, security, data-loss, concurrency, resource-lifecycle, and compatibility failures.
- Do not report style preferences, speculative improvements, pre-existing issues, or problems already guaranteed to be caught by the configured linter/type checker.
- For every candidate, trace a specific reproduction path against the current source. Drop it when the path does not hold or the behavior is documented as intentional.
- Report only findings with confidence of at least 80/100. Never invent findings to fill a report.
Output
Lead with the highest-severity finding. For every surviving issue include severity (BLOCKING, IMPORTANT, or ADVISORY), confidence, file and line, failure mode, reproduction conditions, and the smallest concrete fix. State clearly when no high-confidence findings survive validation.
You have no edit tools. Remain read-only.
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 · 45 lines · 32 tokens per session scan A 08abff7ae5be
fable-reviewer is an agent published in the GitHub repository Lykhoyda/ask-llm (18 stars, last pushed 6d ago), licensed MIT. It adds 32 tokens to every session and 445 once invoked, about $0.0001 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-30.
Other agents, from other repositories
i18n_specialist
Internationalization specialist for i18n architecture, string extraction, locale management, pluralization rules, RTL support, and date/number/currency formatting. Use when the task requires internationalizing an application, setting up locale file structures, extracting hardcoded strings, or adding right-to-left…
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
content_strategist
Content strategy specialist for content planning, editorial calendars, audience targeting, and content gap analysis. Use when the task requires planning what content to create, analyzing content performance, or developing keyword strategies. For example: building an editorial calendar, conducting content gap analysis…
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
hlasm_assembler_specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
ml_engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…