codex-toolkit / scripts
AGENTS.md2 starsChanged 11 days agoMITView on GitHub
The canonical commands are python scripts/validate_skill_pack.py . --as-of YYYY-MM-DD and python scripts/run_smoke_tests.py . --as-of YYYY-MM-DD, run from the repository root with the actual review date. See CONTRIBUTING.md; a static pass does not establish live Codex behavior.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cmdr-chara/chara-toolkitword for word, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cmdr-chara/chara-toolkit★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bin/AGENTS.mdAGENTS.md
- evaluations/AGENTS.mdAGENTS.md
- orchestration/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- skills/llms.txtllms.txt
- bug-finderSkill
- codebase-evolution-controllerSkill
- codebase-improvement-plannerSkill
- completion-proofSkill
- content-provenance-hygieneSkill
- cpp-engineeringSkill
- debugging-investigatorSkill
- delegate-with-mission-cardsSkill
- documentation-synchronizerSkill
- expo-react-native-builderSkill
- flutter-production-builderSkill
- go-engineeringSkill
- kotlin-engineeringSkill
- mobile-architecture-directorSkill
- multi-agent-work-coordinatorSkill
- optimize-codebase-performanceSkill
- product-design-directorSkill
- production-web-builderSkill
- python-engineeringSkill
- repository-intelligenceSkill
- review-and-refactor-codeSkill
- rust-engineeringSkill
- screenshot-to-interfaceSkill
- security-reviewSkill
- swift-engineeringSkill
- toolchain-preflightSkill
- typescript-quality-enforcerSkill
- verification-and-releaseSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Keep the supported script entry points and direct-execution/import behavior intact when changing shared implementations.
- Very specific: line 6
Do not skip failing cases, loosen assertions, suppress warnings, or backdate --as-of to make a result green.
- Distinctive: line 7
Avoid coupling fixture expectations to incidental formatting when the contract is semantic.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validator and helper contracts
- Validators must detect broken contracts, not rewrite evidence or silently repair the inspected input.
- Preserve read-only helper defaults. Any intentional writer needs an explicit output scope, input-preservation checks, and deterministic temporary fixtures.
- Keep the supported script entry points and direct-execution/import behavior intact when changing shared implementations.
- Do not skip failing cases, loosen assertions, suppress warnings, or backdate
--as-ofto make a result green. Report unavailable prerequisites distinctly from a passing check. - Avoid coupling fixture expectations to incidental formatting when the contract is semantic; include rejection cases for unsafe or malformed inputs.
The canonical commands are python scripts/validate_skill_pack.py . --as-of YYYY-MM-DD and python scripts/run_smoke_tests.py . --as-of YYYY-MM-DD, run from the repository root with the actual review date. See CONTRIBUTING.md; a static pass does not establish live Codex behavior.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.