codex-skills
AGENTS.md4 starsChanged 4 months agoMITView on GitHub
This repository manages personal Codex skills, custom agents, and AGENTS.md templates. Skills live in skills/, agent definitions in agents/, templates in templates/, and installation and validation tools in scripts/. Run repository validation after changes and inspect the final diff. For installation changes, verify the affected installed component as well. Define custom agents as standalone TOML files in agents/. Keep reusable templates separate from installed files. Consult docs/wiki/ before non-trivial work when available. Prefer current repository evidence over stale documentation and…
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 repository14 other files it gives its agents.
- build-incrementalSkill
- code-simplifySkill
- create-or-clone-repositorySkill
- design-firstSkill
- implementation-workflowSkill
- manage-git-worktreesSkill
- plan-driven-developmentSkill
- setup-wiki-backed-project-skillsSkill
- subagent-supervisionSkill
- task-briefSkill
- test-driven-debugSkill
- tidy-firstSkill
- write-personal-wikiSkill
- write-project-wikiSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 1 is common, 4 are distinctive, and 0 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
Keep changes focused on the requested component.
- Common: line 12
Do not commit secrets, credentials, or unrelated artifacts.
- Distinctive: line 24
Run repository validation after changes and inspect the final diff.
- Distinctive: line 30
Keep reusable templates separate from installed files.
- Distinctive: line 35
Prefer current repository evidence over stale documentation and capture durable project knowledge there when appropriate.
≈ “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
AGENTS.md
Repository
This repository manages personal Codex skills, custom agents, and AGENTS.md templates.
Skills live in skills/, agent definitions in agents/, templates in templates/,
and installation and validation tools in scripts/.
Rules
- Keep changes focused on the requested component.
- Do not commit secrets, credentials, or unrelated artifacts.
- Install skills through the native Codex plugin; repository scripts manage agents and templates.
Commands
- Validate the repository:
./scripts/verify.sh. - Install agents:
./scripts/install.sh agents --link --backup. - Install templates:
./scripts/install.sh templates --link --backup. - Validate installed components:
./scripts/verify.sh --installed.
Validation
Run repository validation after changes and inspect the final diff. For installation changes, verify the affected installed component as well.
Conventions
Define custom agents as standalone TOML files in agents/.
Keep reusable templates separate from installed files.
Documentation
Consult docs/wiki/ before non-trivial work when available.
Prefer current repository evidence over stale documentation and capture durable
project knowledge there when appropriate.
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.