gap-trap

# gap-trap Sets up a quality framework for repositories where agents write most of the code. Every rule the agents follow has a gate that fails a commit, a push, or a CI run when the rule breaks. A rule a script could check but that names no gate is a defect. The framework is the one described in `reference/framework.md`; read it before either mode. Two modes: `setup` builds the framework in a repo that has none. `refine` audits a repo that has it and proposes the next rules and gates from what broke. Bare `gap-trap` with no keyword means `setup` when the repo has no `AGENTS.project.md`, otherwise `refine`. A hand-written `AGENTS.md` or `CLAUDE.md` on its own is input to setup, not a sign the framework exists. ## Model gate This skill runs on the top coding model of your harness: in Claude Code, Opus or a more capable model (Opus 4.8 or newer, Opus 5, Fable, Mythos); in Codex, the frontier coding model at high or xhigh reasoning effort. Discovery decides which parts of a codebase get a contract, and a wrong contract costs every later session. Your system prompt names your model. If it is a cheaper or faster tier (Sonnet, Haiku, a mini model, or low reasoning effort), stop. Read nothing, write nothing. Say exactly this and end the turn: > gap-trap runs on the top coding model of this harness. You are on > <model name>. Switch with `/model`, then run gap-trap again. Do not dispatch stronger subagents from a weaker orchestrator, start "the easy parts", or offer a lighter ...