codex-fable5

---

FableCodex is a Codex plugin that adds Fable-inspired operating habits to Codex work: inspect first, track goals, record evidence, close review findings, and verify before claiming completion.

It is useful when the cost of a missed step is higher than the cost of a little process.

FableCodex does not clone, unlock, or replace the Fable 5 model. It cannot change model weights, context length, training, or hidden safety systems. It only provides Codex-native workflow guidance, local ledgers, examples, coverage accounting, and optional routing docs.

Quick Start

Install the stable release:

codex plugin marketplace add baskduf/FableCodex --ref v0.5.1
codex plugin add codex-fable5@fablecodex

Restart Codex, then ask for the skill in your prompt:

@codex-fable5 Use this skill to implement the change.
Create a goal ledger if the work has multiple steps.
Track findings before final completion.
Run the project tests before saying it is done.

For a lighter pass:

@codex-fable5 Review this quickly.
Do not create a goal ledger. Check the key evidence and report only actionable findings.

What Changes In Codex

When you invoke @codex-fable5, Codex reads the skill and applies a stricter workflow:

1. Classify the task before acting.
2. Inspect the workspace, files, tools, or cited sources.
3. Use the right Codex-native tools instead of relying on memory.
4. For long work, track goals with evidence checkpoints.
5. For review-sensitive work, track findings and require a final findings gate.
6. Verify with tests, lint, typecheck, screenshots, command output, source inspection, or connector readback.
7. Report what changed, what was verified, and what risk remains.

The skill is procedural. It improves discipline, not raw model capability.

When To Use It

Use it for:

• Multi-step implementation or refactoring.
• Debugging where the root cause is not obvious.
• CI failures, release work, migrations, or security-sensitive changes.
• Reviews where unresolved findings should block final completion.
• Converting Claude/Fable-style prompts into Codex-native guidance.
• Provider-bridge setup when you already have authorized model access.

Skip it for:

• Short answers.
• Tiny single-file edits.
• Brainstorming where no verification is expected.
• Tasks where the extra ledger process would be heavier than the work itself.

How Users Control It

The user controls the skill through the prompt. Be explicit about scope, strictness, verification, and stopping rules.

Strict mode:

@codex-fable5 Run this strictly.
Use a goal ledger, record any review findings, and do not finish until tests and findings gate pass.

Analysis only:

@codex-fable5 Analyze only.
Do not edit files. Give findings with file and line references.

Implementation with limits:

@codex-fable5 Implement the fix.
Do not commit, push, or delete branches.
Run unit tests and report any residual risk.

Debugging:

@codex-fable5 Debug this failure.
Reproduce it first, keep multiple hypotheses, gather disconfirming evidence, then fix and verify.

Goal Ledger

For longer work, the helper stores local state in .codex-fable5/goals.json.

export PATH="$PWD/plugins/codex-fable5/bin:$PATH"

codex-fable5 goals create --brief "Migration" \
  --goal "inspect::Find current behavior and tests" \
  --goal "change::Implement the migration" \
  --goal "verify::Run tests and inspect output"

codex-fable5 goals next

Each completed goal needs evidence:

codex-fable5 goals checkpoint \
  --id G001 \
  --status complete \
  --evidence "Read importer.ts and import.test.ts; current parser rejects quoted commas."

The final goal also requires verification evidence:

codex-fable5 goals checkpoint \
  --id G003 \
  --status complete \
  --evidence "Implemented quoted CSV parsing and updated tests." \
  --verify-cmd "python3 -m unittest discover -s tests -v" \
  --verify-evidence "All tests passed."

Findings Gate

Findings are accepted review issues that must not be lost before final completion. They are stored in .codex-fable5/findings.json.

codex-fable5 findings add \
  --title "Missing final verification" \
  --severity high \
  --source review \
  --location "plugins/codex-fable5/skills/codex-fable5/scripts/codex_goals.py" \
  --evidence "Final checkpoint can complete without proof that tests ran."

Resolve a finding only after the fix and verification are done:

codex-fable5 findings resolve \
  --id F001 \
  --evidence "Final checkpoints now require verification evidence." \
  --verify-cmd "python3 -m unittest discover -s tests -v" \
  --verify-evidence "Regression test passed."

Run the gate before final completion:

codex-fable5 findings gate

The gate fails while open or blocked findings remain. Final goal completion also fails while blocking findings remain.

Command Reference

Without changing PATH, run the checkout helper directly:

plugins/codex-fable5/bin/codex-fable5 status

codex-fable5 update changes only the FableCodex checkout/plugin package. It does not change model access, provider credentials, or hidden runtime behavior. Use codex-fable5 update --ref main only when you intentionally want the development branch instead of the latest stable release.

Install Options

Stable release:

codex plugin marketplace add baskduf/FableCodex --ref v0.5.1
codex plugin add codex-fable5@fablecodex

Development version:

codex plugin marketplace add baskduf/FableCodex --ref main
codex plugin add codex-fable5@fablecodex

Local development:

codex plugin marketplace add ~/Desktop/FableCodex
codex plugin add codex-fable5@fablecodex

Restart Codex after installing or updating the plugin.

Local State

FableCodex writes local task state under .codex-fable5/:

• goals.json: current goal plan and evidence.
• findings.json: review findings and closeout evidence.
• ledger.jsonl: append-only event hist