garbage-man
AGENTS.md8 starsChanged 3 months agoMITView on GitHub
When a user asks to install, run, or use this repository, read and follow plugins/email-cleaner/skills/email-cleanup/SKILL.md. Treat mailbox access as read-only through inventory and review. Prefer an email connector already available to the agent. Otherwise use the read-only IMAP adapter or accept canonical message metadata JSONL. Never ask the user to paste an email password or app password into chat; have them set credentials locally as environment variables. Keep all mailbox metadata and decisions in the user's workspace under .mailroom/, never…
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
When a user asks to install, run, or use this repository, read and follow plugins/email-cleaner/skills/email-cleanup/SKILL.md.
- Very specific: line 7
Keep all mailbox metadata and decisions in the user's workspace under .mailroom/, never in this repository.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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
Email Cleaner agent instructions
When a user asks to install, run, or use this repository, read and follow plugins/email-cleaner/skills/email-cleanup/SKILL.md.
Treat mailbox access as read-only through inventory and review. Prefer an email connector already available to the agent. Otherwise use the read-only IMAP adapter or accept canonical message metadata JSONL. Never ask the user to paste an email password or app password into chat; have them set credentials locally as environment variables.
Keep all mailbox metadata and decisions in the user's workspace under .mailroom/, never in this repository. Do not apply generated rules or alter existing email unless the user separately gives explicit write authorization.
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 28,693 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
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.