agent-manager
AGENTS.md0 starsChanged 8 days agoApache-2.0View on GitHub
agent-manager builds on kagent, Substrate and the agent-platform charts. Before changing it to work around one of them, place the change by the first class that holds: drop (nothing consumes it), upstream already has it (name the mechanism and its configuration), platform (a Giant Swarm product choice, here or in another platform repository), upstream issue (a generic gap that needs design), upstream pull request (a small generic fix), fork-only (a named reason and a dated exit). The full rule is…
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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/zz_generated.base-llm-rules.mdcCursor rule
- .cursor/rules/zz_generated.go-llm-rules.mdcCursor rule
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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: line 12
Do not copy kagent, Substrate or chart rules into this repository.
≈ “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.
Files
AGENTS.md
Upstream placement
agent-manager builds on kagent, Substrate and the agent-platform charts. Before changing it to work around one of them, place the change by the first class that holds: drop (nothing consumes it), upstream already has it (name the mechanism and its configuration), platform (a Giant Swarm product choice, here or in another platform repository), upstream issue (a generic gap that needs design), upstream pull request (a small generic fix), fork-only (a named reason and a dated exit). The full rule is Team Bumblebee's Upstream placement section, kept in its internal plans repository.
- Do not copy kagent, Substrate or chart rules into this repository. Validate by a server-side dry-run of the rendered objects, so the API server's schema, CEL rules and admission policies give the answer.
- A workaround for an upstream gap names the upstream issue or pull request that removes it.
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.