setup
AGENTS.md0 starsChanged 5 days agoMITView on GitHub
This repo is an agent setup for macOS. install.sh copies each tool folder into its home. Claude Code (claude/) is the main agent tool. Design, measure and test each agent change for Claude Code first. Keep the other tool folders (codex/, cursor/, grok/, opencode/) in line with it, but never as critical work: a gap there never blocks or delays a Claude Code change. A tool for agent work, such as bin/agent-stats, reads and reports only Claude Code data. An…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- josechifflet/setupword for word, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- josechifflet/setup★ 0100% 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.
In this repository23 other files it gives its agents.
- codex/AGENTS.mdAGENTS.md
- grok/AGENTS.mdAGENTS.md
- opencode/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- context-doctorSkill
- diagnoseSkill
- handoffSkill
- intentSkill
- paper-useSkill
- retroSkill
- skills-claudeSkill
- ui-principlesSkill
- verify-setupSkill
- wayfinderSkill
- agent-browserSkill
- grillingSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-reviewSkill
- ponytailSkill
- security-auditSkill
- thermo-nuclear-code-quality-reviewSkill
The file
Files
AGENTS.md
This repo is an agent setup for macOS. install.sh copies each tool folder into its home.
Claude Code (claude/) is the main agent tool. Design, measure and test each agent change for Claude Code first. Keep the other tool folders (codex/, cursor/, grok/, opencode/) in line with it, but never as critical work: a gap there never blocks or delays a Claude Code change. A tool for agent work, such as bin/agent-stats, reads and reports only Claude Code data. An audit of Claude Code results or metrics looks only at claude/ and Claude Code data, and its findings and fixes target claude/.
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.