fable-review

fable-review is a skill for Claude Code, Codex from arishofmann/opus-to-fable. It costs 93 tokens per session (488 once invoked), scanned A, original, MIT.

A self-review skill that checks work adversarially before it is finished, committed, or delivered. It looks for correctness problems, edge cases, unsupported assumptions, and regressions.

In plain words
What is it for?
Use it to review code or other output against the request, test error paths and boundary cases, verify evidence for important claims, and fix or report weaknesses.
Why use it?
It provides a deliberate pass for finding mistakes that a normal completion check may miss.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review code or other output against the request, test error paths and boundary cases, verify evidence for important claims, and fix or report weaknesses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arishofmann/opus-to-fable/fable-review
Install

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.

Any agent
npx skills add arishofmann/opus-to-fable --skill fable-review
Clone the repo
git clone --depth 1 https://github.com/arishofmann/opus-to-fable

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for fable-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/arishofmann/opus-to-fable/fable-review/github.svg)](https://agentmods.dev/skills/arishofmann/opus-to-fable/fable-review)
Your own site
<a href="https://agentmods.dev/skills/arishofmann/opus-to-fable/fable-review"><img src="https://agentmods.dev/badge/skills/arishofmann/opus-to-fable/fable-review/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.

agentmods 80×15 button for fable-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/arishofmann/opus-to-fable/fable-review"><img src="https://agentmods.dev/badge/skills/arishofmann/opus-to-fable/fable-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 488 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.00488
Opus 5.5 $0.00037 $0.00195
Sonnet 5.5 $0.00019 $0.00098
Haiku 4.5 $0.00009 $0.00049

Measured 2mo ago against content hash 6513876f2c47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fable-review 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 2mo 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.

dotclaude/skills/fable-review/SKILL.md · 35 lines

What it actually says

Fable Review — adversariale Selbst-Verifikation

Lies dein eigenes Ergebnis so, wie es ein skeptischer Reviewer täte, der einen Fehler finden will — nicht, um die eigene Arbeit zu bestätigen.

Checkliste

  • Korrektheit: Tut der Code / das Ergebnis wirklich, was verlangt war? Zeile für Zeile gegen die Anforderung prüfen.
  • Error-/Edge-Cases: leere Eingaben, null/undefined, Grenzwerte, Nebenläufigkeit, Fehlerpfade — nicht nur der Happy Path.
  • Annahmen: Welche unausgesprochenen Annahmen trägt die Lösung? Welche davon ist unbelegt?
  • Belege: Jede wichtige Behauptung — was ist die Evidenz? Was würde sie widerlegen?
  • Regressionen: Bricht die Änderung etwas Bestehendes? Wurde etwas übersehen oder nur halb erledigt?
  • Ehrlichkeit: Deckt sich ein "fertig/getestet" mit dem tatsächlichen Output (z. B. echten Testläufen)?

Vorgehen

  1. Gehe die Checkliste konkret durch und notiere gefundene Schwächen (mindestens eine).
  2. Fixe, was du fixen kannst; flagge den Rest klar und ehrlich dem Nutzer.
  3. Für hohe Sicherheit: starte 2–3 unabhängige Prüfer-Sub-Agenten (Agent-Tool), jeder mit dem Auftrag, die Lösung zu widerlegen — je eine Linse (Korrektheit / Sicherheit / Edge-Cases). Übernimm nur, was Mehrheit bzw. Belege standhält.

Haltung

Ziel ist, die eigene Arbeit zu brechen, bevor es der Nutzer oder die Produktion tut. Lieber eine echte Schwäche offen benennen als falsche Sicherheit ausstrahlen.

Changes

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.

  1. 2mo ago First seen · 35 lines · 93 tokens per session scan A 6513876f2c47

Subscribe to this mod's changes

fable-review is a skill published in the GitHub repository arishofmann/opus-to-fable (2 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 488 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens