markphelpsmarkphelps/agent-plugins/AGENTS.md

agent-plugins

AGENTS.md5 starsChanged 45 days agoMITView on GitHub

This repository contains multiple plugins. Use progressive disclosure. - mise.toml pins the tool versions. CI resolves them with jdx/mise-action. - Run mise install before npm install in a fresh checkout. - Do not pin a Node version in a workflow file. Change mise.toml instead. - CI runs npm run format:check, npm run validate, and actionlint. Run them locally before you push a change to workflows or plugin manifests.

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,774 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 repository15 other files it gives its agents.
- development/AGENTS.mdAGENTS.md
- cli-designSkill
- codebase-landing-copySkill
- context-file-tuneupSkill
- course-notesSkill
- decision-recordsSkill
- feature-mapSkill
- github-pr-fixupSkill
- github-self-hosted-runnerSkill
- oss-marketingSkill
- oss-repo-readinessSkill
- session-log-auditSkill
- technical-manualSkill
- verify-bugSkill
- whiteboardSkill

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:
Do not manually duplicate edits into top-level skills/ unless sync tooling is unavailable.
line 13
Very specific:
Run mise install before npm install in a fresh checkout.
line 18
Very specific:
Do not pin a Node version in a workflow file.
line 19

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

This repository contains multiple plugins. Use progressive disclosure.

Plugin-Specific Instructions

Development plugin: see development/AGENTS.md

Skill Sync

Skill copies are synced via npm run sync.
Edit plugin-local skill sources first.
Do not manually duplicate edits into top-level skills/ unless sync tooling is unavailable.

Toolchain

mise.toml pins the tool versions. CI resolves them with jdx/mise-action.
Run mise install before npm install in a fresh checkout.
Do not pin a Node version in a workflow file. Change mise.toml instead.
CI runs npm run format:check, npm run validate, and actionlint. Run them locally before you push a change to workflows or plugin manifests.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free