by SihyeonJeon · Claude Skill · ★ 46
why-was-fable-banned English · 한국어 Gate for AI coding agents: blocks edits until a spec passes. The agent can't edit code until it writes and a deterministic gate accepts it: restated goal, non-goals, context chosen by authority, ≥2 rejected alternatives with the boundary each breaks, risks, and runnable acceptance. One shared gate, installed as hooks. Works in Claude Code and Codex. Same prompt, same model — gate off vs on. "Implement a water-current + fish simulation," Opus 4.8, identical prompt both runs: Left (naked) stops at thin ripples.
| Stars | 46 |
| Forks | 10 |
| Language | Python |
| Category | Claude Skill |
| License | MIT |
| Quality Score | 66.4329102601869/100 |
| Last Updated | 2026-06-30 |
| Created | 2026-06-13 |
| Platforms | claude-code, codex, python |
| Est. Tokens | ~15k |
These tools work well together with why-was-fable-banned for enhanced workflows:
Explore other popular claude skill tools:
why-was-fable-banned is Fable-style spec + evidence gate for Claude Code + Codex. Makes Opus/Codex work under Fable-like discipline: blocks every edit until a deterministic spec passes, and there is no "done" without live ac. It is categorized as a Claude Skill with 46 GitHub stars.
why-was-fable-banned is primarily written in Python. It covers topics such as agent-harness, ai-agent-guardrails, ai-coding.
You can find installation instructions and usage details in the why-was-fable-banned GitHub repository at github.com/SihyeonJeon/why-was-fable-banned. The project has 46 stars and 10 forks, indicating an active community.
why-was-fable-banned is released under the MIT license, making it free to use and modify according to the license terms.