agentic-developer-platform / L5-services
AGENTS.md7 starsChanged 6 days agoApache-2.0View on GitHub
Use the modular deployment contract and each service's architecture under docs/l5-services/. - Terraform belongs in this module's infra/<service>/ root, backed by its own state. Reuse infra/modules/ for common code. Do not add new L5 resources or service toggles to gateway/platform Terraform. The existing gateway module call is legacy state compatibility only; preserve it until migration is proven. - Workflow YAML belongs in .github/workflows/; deployment implementation belongs in this module's scripts/. Extend the shared CI and release path. Publish one immutable…
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,843 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- modules/agent-factory/AGENTS.mdAGENTS.md
- modules/domain-apps/superplane/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- evidence-skillSkill
- adp-flowSkill
- grillingSkill
- aidlc-emit-issuesSkill
- codex-bridgeSkill
- stage-1-triageSkill
- stage-2-osintSkill
- stage-3-staticSkill
- stage-4-dynamicSkill
- stage-5-correlationSkill
- stage-6-verdictSkill
- stage-7-reportSkill
- url-analysisSkill
- url-analysisSkill
- skypilotSkill
- superplaneSkill
The file
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
Use the modular deployment contract and each service's architecture under docs/l5-services/.
- Very specific: line 22
Run the relevant Terraform mock tests, deployment tests and changed runtime tests.
≈ “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
L5 implementation boundaries
Use the modular deployment contract
and each service's architecture under docs/l5-services/.
- Terraform belongs in this module's
infra/<service>/root, backed by its own state. Reuseinfra/modules/for common code. Do not add new L5 resources or service toggles to gateway/platform Terraform. The existing gateway module call is legacy state compatibility only; preserve it until migration is proven. - Workflow YAML belongs in
.github/workflows/; deployment implementation belongs in this module'sscripts/. Extend the shared CI and release path. Publish one immutable package, install selected roots, then qualify each service independently. - Scope workers, repair scans and queue routing by durable service ownership. Product APIs and the broker continue to govern customer provider resources.
- Infrastructure installation, code rollout and native qualification are distinct outcomes. Keep unqualified consumers disabled; retain run/outbox history.
- The remaining release stories own runtime assembly, their service drivers, installation readback and live acceptance. An artifact-only workflow is insufficient.
- Planning file lists are explanatory. Additional necessary files are allowed; a path missing from that list is not a reason to fail a node.
Run the relevant Terraform mock tests, deployment tests and changed runtime tests.
Public documentation stays under docs/l5-services/ and follows docs/PUBLISHING.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.