harlan-zwharlan-zw/brundlefly/AGENTS.md

brundlefly

AGENTS.md7 starsChanged 32 days agoMITView on GitHub

Self-contained Agent Skills collection with a shared body horror mascot. Skills are Markdown instructions. There is no runtime build step. Every skill must work when its directory is copied alone. Keep required references, scripts, templates, and licenses inside that directory. Use relative paths for bundled files. Do not depend on another skill from a personal collection. Do not require a private account or personal checkout. Use the standard name and description frontmatter fields. The name must match the containing directory.…

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 repository12 other files it gives its agents.
- claim-fidelitySkill
- claritySkill
- copywritingSkill
- glossarySkill
- im-not-a-humanSkill
- im-part-humanSkill
- pull-request-summarySkill
- readmeSkill
- release-notesSkill
- slop-naming-recoverySkill
- technical-guideSkill
- verify-examplesSkill

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

17 rules. About 0 are common, 17 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Read GLOSSARY.md before naming a skill, product concept, or brand term.
line 8
Distinctive:
Read COPY.md before writing public copy or skill prose.
line 9
Distinctive:
Read VISION.md before changing scope or adding claims.
line 10
Distinctive:
Read CONTRIBUTING.md before adding a skill.
line 11
Distinctive:
Read brand rules before changing visual assets.
line 12
Distinctive:
Read repository conventions before changing structure.
line 13
Distinctive:
Read quality comparisons before proposing evaluations or competitor claims.
line 14
Distinctive:
Every skill must work when its directory is copied alone.
line 18
Distinctive:
Keep required references, scripts, templates, and licenses inside that directory.
line 19
Distinctive:
Use relative paths for bundled files.
line 20
Distinctive:
Do not depend on another skill from a personal collection.
line 21
Distinctive:
Do not require a private account or personal checkout.
line 22
Distinctive:
Use the standard name and description frontmatter fields.
line 24
Distinctive:
Keep the main instructions short and move detailed material into references when useful.
line 27
Distinctive:
Use assets/brand for current artwork.
line 32
Distinctive:
Use assets/source for high-resolution masters.
line 33
Distinctive:
Use assets/archive only for historical design reference.
line 34

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

Brundlefly

Self-contained Agent Skills collection with a shared body horror mascot. Skills are Markdown instructions. There is no runtime build step.

Read first

Read GLOSSARY.md before naming a skill, product concept, or brand term.
Read COPY.md before writing public copy or skill prose.
Read VISION.md before changing scope or adding claims.
Read CONTRIBUTING.md before adding a skill.
Read brand rules before changing visual assets.
Read repository conventions before changing structure.
Read quality comparisons before proposing evaluations or competitor claims.

Skill boundaries

Every skill must work when its directory is copied alone. Keep required references, scripts, templates, and licenses inside that directory. Use relative paths for bundled files. Do not depend on another skill from a personal collection. Do not require a private account or personal checkout.

Use the standard name and description frontmatter fields. The name must match the containing directory. Describe the task and its trigger in plain words. Keep the main instructions short and move detailed material into references when useful.

Branding

The corrected full-arm banner is the canonical banner. Use assets/brand for current artwork. Use assets/source for high-resolution masters. Use assets/archive only for historical design reference. Preserve the four arms, two legs, and two wings. Confirm additional public slogans and decorative text with the owner.

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