ai-rules
AGENTS.md134 starsChanged 9 months agoApache-2.0View on GitHub
Firebender supports overlay configuration files. To customize your configuration: firebender.json is generated as supplemental config when ai-rules/mcp.json and/or ai-rules/firebender-overlay.json exists. MCP Integration: If you have ai-rules/mcp.json, the MCP servers are merged into firebender.json first, then the overlay is applied. This allows you to override MCP configurations in the overlay if needed. Codex supports overlay configuration files. To customize your configuration: .codex/config.toml is generated when ai-rules/mcp.json and/or ai-rules/codex-config.toml exists. MCP Integration: If you have ai-rules/mcp.json, the MCP servers are converted into…
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,542 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Example/single_agents_md/ai-rules/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- debuggingSkill
- stars-we-preferSkill
The file
We split this agents.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Create ai-rules/firebender-overlay.json in the same parent directory as your generated firebender.json
- Very specific: line 28
MCP Integration: If you have ai-rules/mcp.json, the MCP servers are merged into firebender.json first, then the overlay is applied.
- Very specific: line 39
MCP Integration: If you have ai-rules/mcp.json, the MCP servers are converted into Codex [mcp_servers] TOML first, then the overlay is …
≈ “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
Supported AI Coding Agents
Agent Compatibility Table
| Agent | Standard Mode | Symlink Mode | MCP Support | Notes |
| AMP | AGENTS.md -> inlined file | AGENTS.md -> ai-rules/AGENTS.md | - | |
| Claude Code | CLAUDE.md -> inlined file | CLAUDE.md -> ai-rules/AGENTS.md | .mcp.json | |
| Cline | .clinerules/AGENTS.md -> inlined file | .clinerules/AGENTS.md -> ../ai-rules/AGENTS.md | - | |
| Codex | AGENTS.md -> inlined file | AGENTS.md -> ai-rules/AGENTS.md | .codex/config.toml | Optional ai-rules/codex-config.toml overlay supported |
| Copilot | AGENTS.md -> inlined file | AGENTS.md -> ai-rules/AGENTS.md | - | |
| Cursor | .cursor/rules/*.mdc | AGENTS.md -> ai-rules/AGENTS.md | .cursor/mcp.json | Symlink mode: only project root level |
| Firebender | AGENTS.md -> inlined file | AGENTS.md -> ai-rules/AGENTS.md | firebender.json | Commands live in .firebender/; skills reuse .agents/skills; overlay supported |
| Gemini | GEMINI.md -> inlined file | GEMINI.md -> ai-rules/AGENTS.md | Embedded in .gemini/settings.json | |
| Goose | AGENTS.md -> inlined file | AGENTS.md -> ai-rules/AGENTS.md | - | |
| Kilocode | .kilocode/rules/AGENTS.md -> inlined file | .kilocode/rules/AGENTS.md -> ../../ai-rules/AGENTS.md | - | |
| Roo | .roo/rules/AGENTS.md -> inlined file | .roo/rules/AGENTS.md -> ../../ai-rules/AGENTS.md | .roo/mcp.json |
Firebender Overlay Support
Firebender supports overlay configuration files. To customize your configuration:
- Create
ai-rules/firebender-overlay.jsonin the same parent directory as your generatedfirebender.json - Any values defined in the overlay file will be merged into the base configuration, with overlay values taking precedence
firebender.json is generated as supplemental config when ai-rules/mcp.json and/or ai-rules/firebender-overlay.json exists.
MCP Integration: If you have ai-rules/mcp.json, the MCP servers are merged into firebender.json first, then the overlay is applied. This allows you to override MCP configurations in the overlay if needed.
Codex Overlay Support
Codex supports overlay configuration files. To customize your configuration:
- Create
ai-rules/codex-config.tomlin the same parent directory as your generated.codex/config.toml - Any values defined in the overlay file will be merged into the generated Codex configuration, with overlay values taking precedence
.codex/config.toml is generated when ai-rules/mcp.json and/or ai-rules/codex-config.toml exists.
MCP Integration: If you have ai-rules/mcp.json, the MCP servers are converted into Codex [mcp_servers] TOML first, then the overlay is applied. This allows you to override MCP configurations in the overlay if needed.
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.