Agent-Skills / Infrastructure
AGENTS.md9 starsChanged 46 days agoApache-2.0View on GitHub
- Treat this subtree as the factory plane for ask, validation, schemas, fixtures, tests, sync, projection, packaging, and governance mechanics. - Keep public repo operations routed through root ./bin/ask; edit Infrastructure/bin/ask and implementation modules only when changing the command machinery itself. - When changing CLI behavior, schemas, generated receipts, or SDK contracts, update implementation, tests, fixtures, and docs together. - For technical work, read the root CODESTYLE.md before editing. If a narrower module document exists, follow it as well. -…
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 repository93 other files it gives its agents.
- AGENTS.mdAGENTS.md
- artifacts/AGENTS.mdAGENTS.md
- Docs/AGENTS.mdAGENTS.md
- logs/AGENTS.mdAGENTS.md
- Plugins/AGENTS.mdAGENTS.md
- Skills/AGENTS.mdAGENTS.md
- skills-system/AGENTS.mdAGENTS.md
- Wiki/AGENTS.mdAGENTS.md
- SKILL.mdSkill
- agents-mdSkill
- alignment-checkpointSkill
- autofixSkill
- autoresearchSkill
- autoreviewSkill
- bash-hygieneSkill
- biome-lintingSkill
- bootstrapSkill
- code-fixes-triageSkill
- codex-agent-creatorSkill
- codex-automation-architectSkill
- codex-environment-creatorSkill
- codex-hooks-builderSkill
- codex-reviewSkill
- coding-harnessSkill
- context7Skill
- decide-build-primitiveSkill
- diagram-cliSkill
- elixir-proSkill
- evals-routerSkill
- fix-miseSkill
- frontend-designSkill
- goal-governorSkill
- goSkill
- improve-agent-nativeSkill
- improve-codebase-architectureSkill
- insight-reportSkill
- javascript-proSkill
- keep-codex-fastSkill
- npm-releaseSkill
- pnpm-managerSkill
- prek-proSkill
- pr-green-sweepSkill
- production-deploymentSkill
- project-brainSkill
- rust-proSkill
- sdk-scenario-generatorSkill
- session-workflow-minerSkill
- simplifySkill
- skill-pr-deliverySkill
- technical-writerSkill
- testingSkill
- tomlSkill
- triageSkill
- typescriptSkill
- ubiquitous-languageSkill
- unslopifySkill
- user-documentationSkill
- uv-python-project-setupSkill
- valeSkill
- verification-before-completionSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 14
Treat this subtree as the factory plane for ask, validation, schemas, fixtures, tests, sync, projection, packaging, and governance …
- Very specific: line 16
Keep public repo operations routed through root ./bin/ask.
- Distinctive: line 19
When changing CLI behavior, schemas, generated receipts, or SDK contracts, update implementation, tests, fixtures, and docs together.
- Distinctive: line 23
Keep canonical source and runtime projection lanes separate.
- Distinctive: line 35
Prefer repo wrappers and targeted tests over ad hoc commands.
≈ “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
Infrastructure Agent Guide
Scope
- Applies to
Infrastructure/**. - Inherits the repository root AGENTS.md.
Edit Policy
- Treat this subtree as the factory plane for
ask, validation, schemas, fixtures, tests, sync, projection, packaging, and governance mechanics. - Keep public repo operations routed through root
./bin/ask; editInfrastructure/bin/askand implementation modules only when changing the command machinery itself. - When changing CLI behavior, schemas, generated receipts, or SDK contracts, update implementation, tests, fixtures, and docs together.
- For technical work, read the root CODESTYLE.md before editing. If a narrower module document exists, follow it as well.
- Keep canonical source and runtime projection lanes separate. Do not use generated projections as implementation source.
Context Pointers
- Infrastructure scripts map: scripts/README.md.
- Path ownership: ../Docs/agents/14-path-ownership-boundaries.md.
- Validation contract: ../Docs/agents/04-validation.md.
- Skill lifecycle rules: ../Docs/agents/17-skill-management.md.
Validation
- Prefer repo wrappers and targeted tests over ad hoc commands.
- For Python changes, run the nearest targeted
pytestpath underInfrastructure/tests/**before widening. - For schema or fixture changes, run the owning validator and include exact
pass,fail, orblockedoutcomes.
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.