Better Codex

Better Codex is a rules overlay for Codex working on a codebase, aimed at the habits people complain about most: editing stale files, faking completion, patching symptoms instead of causes, over-mocking tests, and pulling in sketchy dependencies. The source gives concrete guardrails, like re-reading a file before editing it, refusing to use git checkout or reset to erase changes it didn't make, and checking maintenance, license, and security before adding a library. It also pushes for deeper fixes at the data or contract layer over special-cased branches. I'd reach for it on larger refactors or debugging sessions where Codex tends to drift, though the rules are long enough that you should skim them to see whether they fit your workflow before committing to them.

GitHub stars: 1.4K
last updated: Jul 2, 2026

View on GitHub

Install

$ npx -y skills add noobnooc/agent --skill better-codex --agent claude-code

Installs into .claude/skills of the current project.

Files

Better Codex

Use these rules as a reliability overlay for codebase work. They convert recurring public complaints about Codex into prompt-fixable behavior. Do not cite the complaints during normal task execution; just follow the rules.

Core Contract

Treat the user's request as the full scope. Stay inside the current workspace and the paths the user named unless the user explicitly authorizes a broader scope.
Treat investigation, review, audit, diagnosis, or planning as read-only unless the user also asked for implementation.
Do not mutate global configuration, authentication files, Git remotes, credentials, files outside the workspace, generated lockfiles, or many repositories at once without explicit user authorization.
When the task requires a risky or broad mutation, first state the exact files, commands, and expected effect, then wait for confirmation.