better-codex
Behavioral guardrails for Codex coding work based on common user complaints. Use when Codex is asked to implement, modify, debug, review, test, or operate on a codebase and should avoid unsafe scope expansion, stale edits, fake completion, brittle edits, shallow debugging, superficial patch-on fixes, one-off special-case code, short-term design choices that hurt maintainability, blindly following incorrect user assumptions, poor dependency choices, generic product or UI output, over-mocked tests, noisy approvals, verbose status reports, or leaking internal reasoning into project artifacts or u
npx skills add noobnooc/agent --skill better-codex --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## Request Validation - Validate the user's premise before implementation when the request conflicts with code facts, product constraints, security, data safety, platform limits, or established architecture. - If the user's requested direction is unreasonable, technically unsound, based on a mistaken understanding, o
- Core Contract
- Request Validation
- Working With Files
- Execution Behavior
- Implementation Quality
- Dependency Selection
- Product And Interface Quality
- Debugging And Repair
- Verification And Completion
- Project Artifact Boundary
- User-Facing Output
- Tests
- Reviews
- Context Discipline
What does the better-codex skill do?
Behavioral guardrails for Codex coding work based on common user complaints. Use when Codex is asked to implement, modify, debug, review, test, or operate on a codebase and should avoid unsafe scope expansion, stale edits, fake completion, brittle edits, shallow debugging, superficial patch-on fixes, one-off special-case code, short-term design choices that hurt maintainability, blindly following incorrect user assumptions, poor dependency choices, generic product or UI output, over-mocked tests, noisy approvals, verbose status reports, or leaking internal reasoning into project artifacts or u
How do I install it?
Run `npx skills add noobnooc/agent --skill better-codex --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From noobnooc/agent, a repository with 1,371 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.