agentops / cli
AGENTS.md453 starsChanged 4 months agoApache-2.0View on GitHub
Inherit the root operating contract, including its BD identity, private-history preservation, validation, and delivery-authority rules. - CLI architecture: before changing command composition, gates, or evidence boundaries, read the Go CLI architecture. - Tracker work: follow the root's repository-tracker section. The root .beads/redirect also applies here. Git and Dolt synchronization follow that store's configured policy; discover the actual remote before any authorized push. Preserve the pre-migration .beads estate as well as _beads history. A BV recommendation authorizes neither a claim, parallel…
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 repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-nativeSkill
- agy-nativeSkill
- architectureSkill
- claude-execSkill
- codex-execSkill
- councilSkill
- craft-goalSkill
- docSkill
- domainSkill
- ergonomicsSkill
- idea-genieSkill
- implementSkill
- interviewSkill
- memorySkill
- navigateSkill
- orchestrateSkill
- planSkill
- postmortemSkill
- premortemSkill
- refactorSkill
- researchSkill
- reverse-engineerSkill
- reviewSkill
- rpiSkill
- securitySkill
- skill-builderSkill
- skill-evalSkill
- testSkill
- triageSkill
- using-gcSkill
- validateSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
CLI architecture: before changing command composition, gates, or evidence boundaries, read the Go CLI architecture.
- Very specific: line 8
Tracker work: follow the root's repository-tracker section.
- Very specific: line 13
Go changes: follow the root's focused-check, build, vet, test, and lint requirements.
≈ “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
CLI subtree
Inherit the root operating contract, including its BD identity, private-history preservation, validation, and delivery-authority rules.
- CLI architecture: before changing command composition, gates, or evidence boundaries, read the Go CLI architecture.
- Tracker work: follow the root's repository-tracker section. The root
.beads/redirectalso applies here. Git and Dolt synchronization follow that store's configured policy; discover the actual remote before any authorized push. Preserve the pre-migration.beadsestate as well as_beadshistory. A BV recommendation authorizes neither a claim, parallel write, nor closure. - Go changes: follow the root's focused-check, build, vet, test, and lint
requirements. Commands in Makefile run from
cli/; from any directory, usemake -C /absolute/path/to/agentops/cli <target>.
Finish only with evidence for the changed behavior and all required checks;
report unchecked acceptance through the root's NOT_PROVEN rule.
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.