.agents
AGENTS.md6 starsChanged 50 days agoApache-2.0View on GitHub
.agents/ is the canonical source. templates/ may contain only host-specific differences; do not duplicate canonical content there. Run asdf install shfmt or asdf install bats when a tool is unavailable. These constraints protect canonical source files and installed host views.
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 33,315 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 repository35 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- audit-agentSkill
- babysit-prSkill
- check-dependabotSkill
- compare-itSkill
- context-filesSkill
- create-prSkill
- delegate-workSkill
- explain-itSkill
- git-commitSkill
- improve-selfSkill
- isolate-cliSkill
- jira-syntaxSkill
- log-changesSkill
- make-docsSkill
- make-skillSkill
- manage-adrSkill
- manage-issuesSkill
- manage-ticketsSkill
- manage-todoSkill
- monitor-ciSkill
- prove-checksSkill
- research-itSkill
- review-archSkill
- review-implSkill
- review-specSkill
- scan-securitySkill
- search-webSkill
- split-docsSkill
- test-goSkill
- test-tsSkill
- verify-implSkill
- vet-dependencySkill
- writing-plansSkill
- writing-specsSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
13 rules. About 0 are common, 3 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before finishing any change: make check (runs every CI gate from ci.yml locally)
- Very specific: line 8
After changing scripts/install.sh or installer behavior: bats test/
- Very specific: line 9
Before finishing a shell-script change: shfmt -d scripts
- Very specific: line 10
Before finishing an installer change: shellcheck scripts/install.sh
- Very specific: line 12
Run asdf install shfmt or asdf install bats when a tool is unavailable.
- Very specific: line 30
Keep behavior shared by hosts in .agents/.
- Very specific: line 31
Run make validate after changing a skill.
- Distinctive: line 32
Follow the surrounding style.
- Distinctive: line 34
Treat every checkout outside the assignment as read-only.
- Very specific: line 35
Write scratch files to the session scratchpad or a mktemp -d directory, never inside this repository.
- Very specific: line 37
Run a negative control before reporting any green.
- Distinctive: line 52
Run the destructive git commands the Working Agreement lists under "Surgical Changes".
- Very specific: line 53
Write into an installed host directory.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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
.agents/ is the canonical source. templates/ may contain only host-specific differences; do not duplicate canonical content there.
Commands
- Before finishing any change:
make check(runs every CI gate from ci.yml locally) - After changing
scripts/install.shor installer behavior:bats test/ - Before finishing a shell-script change:
shfmt -d scripts - Before finishing an installer change:
shellcheck scripts/install.sh
Run asdf install shfmt or asdf install bats when a tool is unavailable.
Gotchas
- The installer skips a host whose root directory does not exist; inspect its output.
--rulesdoes not remove stale destination files. Legacy Working Agreement cleanup happens only after a successful--contextinstallation.- A Claude
pathsoverlay marks a rule that must not become an OpenCode global instruction. --contextoverwrites the host-native context file and removes only legacy rules that match the canonical content.lint,typecheckand the other file-selecting gates readgit ls-files; an untracked file is skipped silently and the gate can still exit 0. Stage it first.- Everything tracked under
.agents/skills/ships to five host directories; keep tests and fixtures intest/, which ships nowhere. make validateapplies its 17,500-byte ceiling to the skill body, not toSKILL.mdas a file:split_frontmatterhands_check_bodyonly the text after the closing---. No gate lints a skill as Markdown either;lint-markdownselectsREADME.mdanddocs/.
Boundaries
These constraints protect canonical source files and installed host views.
Always
- Keep behavior shared by hosts in
.agents/; add host-specific frontmatter or prompt fragments only intemplates/. - Run
make validateafter changing a skill. - Follow the surrounding style. Do not refactor adjacent legacy content without a separate task.
- Work in the assigned checkout or worktree. A separate worktree is optional; preserve other sessions' changes in a shared checkout.
- Treat every checkout outside the assignment as read-only. Run runtime tests and mutation controls in an isolated scratch copy.
- Write scratch files to the session scratchpad or a
mktemp -ddirectory, never inside this repository. Delete your own directory when you finish, and move anything that must outlive the task into.tasks/. - Stage a new file with
git add <path>before running any gate, for the reason under Gotchas: the file-selecting gates readgit ls-files, skip an untracked file, and still exit 0. - Run a negative control before reporting any green.
prove-checksowns what that requires. - Land a delegate's branch only in the form you were asked for. Verification finishes the work; it does not authorize merging, pushing, or opening a PR. When the form was not named, ask before the branch moves anywhere.
Ask first
- Changes to host-wide settings in
.claude/,.gemini/, or.opencode/. - Installer destinations or stale-file migration behavior.
- Canonical skill content, its validators, or vendor templates.
- Any write outside the assigned checkout or worktree.
Never
- Put a project-specific fact into any artifact here. Everything tracked in this repository installs into every project on the host, so a repository or service name, a schema, a port, a ticket prefix or a team convention belongs in that project's own context file; this repository carries only what is explicitly useful to every project.
- Edit installed files under
$HOMEas a substitute for updating this source repository. - Copy a path-scoped Claude rule into OpenCode's global rules.
- Run the destructive git commands the Working Agreement lists under "Surgical Changes". In a shared checkout they destroy a parallel session's uncommitted work.
- Write into an installed host directory.
sync_contextinscripts/install.shnames them:$HOME/.claude,$HOME/.codex,$HOME/.copilot,$HOME/.gemini,$HOME/.config/opencode. - Revert or reformat a change you cannot trace to your own brief.
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.

