ai-skills
AGENTS.md2 starsChanged 6 months agoMITView on GitHub
This repository ships AI coding assistant configurations in two delivery formats: The legacy .claude/ package was removed in v0.2.0 — plugin/ fully replaces it for Claude Code. This file is your (Codex's) instructions for working in the .codex/ and shared .agents/ directories. After v0.2.0, parity is enforced between Codex and Windsurf only — Claude Code lives in plugin/ and follows its own internal organization. Every role, skill, and guardrail in .codex/ must have a matching entry in .windsurf/. The parity…
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 32,671 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 repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
After v0.2.0, parity is enforced between Codex and Windsurf only — Claude Code lives in plugin/ and follows its own internal organization.
- Distinctive: line 71
all asset contents must be in English
- Distinctive: line 73
use relative runtime paths, never absolute user paths
- Very specific: line 76
update review/parity-matrix.md for any Codex ↔ Windsurf parity-impacting change
- Distinctive: line 77
remove project-specific assumptions from shared assets
- Distinctive: line 78
prefer runtime-native representations over forced file mirroring
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
AI Assets Repository — Codex Instructions
This repository ships AI coding assistant configurations in two delivery formats:
plugin/— full Claude Code plugin (canonical source of truth for Claude Code; current version inplugin/.claude-plugin/plugin.json)..codex/+.windsurf/+.agents/— copy-ready three-package layout for OpenAI Codex and Codeium Windsurf (your runtime).
The legacy .claude/ package was removed in v0.2.0 — plugin/ fully replaces it for Claude Code. This file is your (Codex's) instructions for working in the .codex/ and shared .agents/ directories.
Quick Reference
ai-skills/
├── plugin/ # Claude Code plugin — DO NOT MIRROR INTO .codex/
├── .agents/skills/ # 39 skills (shared between Codex and Windsurf)
├── .codex/ # Codex runtime package (your home)
│ ├── roles/ # 22 role definitions (mirrors .windsurf/rules/roles/)
│ ├── rules/ # 8 rule files + role overlays
│ ├── operations/ # hook-intents, launch-reference, settings-mapping, source-sync, skill-role-mapping
│ ├── templates/ # 14 AGENTS.md scaffolds
│ └── checklists/ # review checklists
├── .windsurf/ # Windsurf runtime package (parity target)
│ ├── rules/roles/ # 22 role files (mirrors .codex/roles/)
│ ├── skills/ # 39 skills (mirrors .agents/skills/)
│ ├── workflows/ # 27 user-facing workflow files
│ └── hooks/ # Python scripts + configs
├── review/parity-matrix.md # Codex ↔ Windsurf alignment tracker
├── install.sh # bash installer (Codex + Windsurf only — Linux/macOS)
└── install.ps1 # PowerShell installer (Codex + Windsurf only — Windows)Core Concepts
Two-Vendor Parity (Codex ↔ Windsurf)
After v0.2.0, parity is enforced between Codex and Windsurf only — Claude Code lives in plugin/ and follows its own internal organization. Every role, skill, and guardrail in .codex/ must have a matching entry in .windsurf/. The parity matrix (review/parity-matrix.md) tracks alignment.
Capability mapping:
- Codex roles = Windsurf roles
.agents/skills/=.windsurf/skills/- Codex operations (documented intent) = Windsurf hooks (scripts + hooks.json)
- Codex templates = Windsurf skill-embedded resources
See PARITY.md for the full parity model.
Codex Package Layout
.codex/
├── roles/ # role definitions (one per file)
├── rules/ # guardrails and standards
├── operations/ # hook intent docs, launch reference, settings mapping
├── templates/ # AGENTS.md scaffolds per tech stack
├── checklists/ # review checklists
├── config.toml # package configuration
└── instructions.md # maintenance rulesCodex has no native hook execution. .codex/operations/hook-intents.md documents what the equivalent Windsurf/Claude Code hooks enforce so Codex reviewers can verify intent compliance manually.
Skill Format
Skills live in .agents/skills/<name>/SKILL.md with YAML frontmatter. Resource files sit alongside the skill file. Codex and Windsurf both read from .agents/skills/.
Installers
install.sh and install.ps1 sync .agents/, .codex/, .windsurf/ to ~/. Claude Code is installed separately via claude --plugin-dir ./plugin (not these scripts).
Editing Rules
- all asset contents must be in English
- SKILL.md and rule files have a 12,000 character limit (skill resources have no hard limit but should stay focused)
- use relative runtime paths, never absolute user paths
- new Codex roles/skills/guardrails must be added to Windsurf simultaneously (and vice versa)
- new plugin assets land in
plugin/only — there is no longer a.claude/mirror to keep in sync - update
review/parity-matrix.mdfor any Codex ↔ Windsurf parity-impacting change - remove project-specific assumptions from shared assets
- prefer runtime-native representations over forced file mirroring
- the
@humanizerskill must be applied to all public-facing content
Common Tasks
| Task | What to do |
| Add a Codex/Windsurf skill | Create SKILL.md in .agents/skills/ and .windsurf/skills/. Add workflow in .windsurf/workflows/ if user-invocable. Update parity matrix |
| Add a Codex/Windsurf role | Create role in .codex/roles/, role in .windsurf/rules/roles/. Update parity matrix |
| Add a Codex/Windsurf guardrail | Create rule in .codex/rules/, .windsurf/rules/. If hook-backed, document intent in .codex/operations/hook-intents.md and add Python script + config in .windsurf/hooks/ |
| Add a Codex template | Create in .codex/templates/. Windsurf embeds templates inside skill resources |
| Touch Claude Code assets | Edit in plugin/ directly — do NOT mirror into .codex/ or .windsurf/ |
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.

