agent-orchestrator
AGENTS.md0 starsChanged 41 days agoApache-2.0View on GitHub
This repository contains AGENT ORCHESTRATOR's portable plugin and optional Codex profiles. Keep changes scoped and preserve unrelated edits. Do not alter the user's global configuration, install dependencies or launch network services as part of ordinary package maintenance. Read docs/README.md for the lifecycle, capability boundaries and publication process. Keep narrative documentation under docs/; retain this file, README.md and skills/*/SKILL.md at their required entry locations. The coordinator owns integration. Delegate independent analysis/review when useful, with explicit ownership and permitted side effects. Inspect…
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 repository14 other files it gives its agents.
- business-operationsSkill
- capability-managerSkill
- decision-routingSkill
- global-orchestratorSkill
- integration-builderSkill
- plugin-safety-reviewSkill
- project-designSkill
- project-discoverySkill
- project-documentationSkill
- project-evidence-reviewSkill
- project-knowledgeSkill
- project-qaSkill
- project-releaseSkill
- project-securitySkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read docs/README.md for the lifecycle, capability boundaries and publication process.
≈ “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
Repository guidance
This repository contains AGENT ORCHESTRATOR's portable plugin and optional Codex profiles. Keep changes scoped and preserve unrelated edits. Do not alter the user's global configuration, install dependencies or launch network services as part of ordinary package maintenance.
Read docs/README.md for the lifecycle, capability boundaries and publication process. Keep narrative documentation under docs/; retain this file, README.md and skills/*/SKILL.md at their required entry locations.
The coordinator owns integration. Delegate independent analysis/review when useful, with explicit ownership and permitted side effects. Inspect actual evidence before accepting agent output. External A2A requires an explicitly selected, authorized service.
Package checks require Rust 1.94.1+ and Git:
cargo fmt --check
cargo clippy --locked --all-targets -- -D warnings
cargo test --locked --lib --tests
cargo run --locked -- validate-package --root .Tests create and clean isolated Git fixtures under the system temporary directory. These verify the evidence checker; they do not prove a user's application passed E2E. Review affected skills, references, metadata and permission boundaries independently. Exclude caches, credentials and personal configuration from release archives. Preserve Apache-2.0 license and attribution. Push, submission and publication require the intended target and the user's authorization; verify actual hosted CI after an authorized push.
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.