Fable
Run Claude Fable 5 on Opus 4.8 in Claude Code. The Mythos-class model pulled by export controls — brought back as a native agentic distillation (FABLE_CODE.md), measured playbook, verification hooks, and design/MCP/test skills. "Fable 5 Lite," done right.
npx -y skills add codeclawd/fable-mode --skill fableAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Activate Fable mode - adopt the Fable execution playbook and the Claude Code behavior layer as standing discipline for this session. Use when the user types /fable, says "fable mode", "use fable", "work like fable", or asks for maximum-discipline execution - and PROACTIVELY at the start of any non-trivial engineering task (multi-step implementation, refactor, migration, long debugging session) when the playbook is not already in context.
SKILL.md
1.8 KB, as published. Nobody here has run it
Fable mode
Activate the full Fable discipline for the rest of this session:
- Read
~/.claude/FABLE_PLAYBOOK.md(execution discipline: reason before acting, observe-then-decide, verify every edit, communication floor, grounding protocol). - Read
~/.claude/FABLE_CODE.md(the Claude Code behavior layer: final-message contract, readable-over-concise, tool discipline, autonomy and honesty rules). If either file is missing, the install is broken — don't hunt for other copies. Tell the user to runfable doctor(or re-runpython install.pyfrom the fable-mode checkout), then continue with the task, applying whatever Fable discipline is already in context. - Adopt both as standing discipline — they govern every subsequent turn of this session, not just the next reply.
- Confirm activation in one line ("Fable mode active — playbook and behavior layer loaded."), then continue with the user's task. Do not summarize the documents back.
If the playbook is already in this context (look for a "Fable mode active"
injection from the hook), skip the reads: confirm activation in one line and
apply FABLE_CODE.md from context, reading it only if absent.
Scale the heavier machinery to the task: the evidence ledger and the
grounding-verifier agent are for non-trivial or hard-to-reverse work, not for
typo fixes (the playbook's own calibration rules apply).