skills
AGENTS.md1 starsChanged 49 days agoMITView on GitHub
Agent policy/workflow/skills layer. Read docs/CROSS-PROJECT-LESSONS-2026-09.md before making architectural changes. Before proposing architecture or cross-project primitives, read: Do not repeat research already indexed unless new evidence or requirements materially change the conclusion. New architecture proposals must identify: - the invariant uniquely owned by the new layer - why a lower existing layer cannot own it - what duplicated state or layer the proposal removes Key constraints include: - visibility is not durability - identity, order, content hash, and presentation remain distinct…
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 repository113 other files it gives its agents.
- ac-ideateSkill
- ac-listSkill
- ac-roadmapSkill
- agentbridge-mcpSkill
- almanacSkill
- almquist-shellSkill
- ansible-fleetSkill
- apfsSkill
- apple-siliconSkill
- arena-actorsSkill
- asustor-nasSkill
- a-teamSkill
- atem-miniSkill
- at-tuiSkill
- autoresearchSkill
- babysitSkill
- bonzibuddySkill
- bop-brainstormSkill
- bop-catalogSkill
- bop-onSkill
- bop-teamSkill
- bop-workflowSkill
- bsd-portabilitySkill
- code-refactoringSkill
- codex-personasSkill
- context-graphSkill
- councilSkill
- datadog-backupSkill
- dd-tagsSkill
- delegateSkill
- deming-pdsaSkill
- deterministic-replaySkill
- dispatch-nuSkill
- durable-commitSkill
- elixir-gastown-opsSkill
- ergo-ircSkill
- esp32-tang-bridgeSkill
- fleet-evalSkill
- fleet-ircSkill
- freebsd-build-vmSkill
- freebsd-piSkill
- freebsdSkill
- ganttSkill
- gastown-opsSkill
- gastown-slingSkill
- gh-authSkill
- gitea-releaseSkill
- gitea-runnerSkill
- henshuSkill
- irclaw-cluster-opsSkill
- irclaw-research-teamSkill
- irc-taskSkill
- jail-factorySkill
- jjSkill
- jobcard-systemSkill
- kubernetesSkill
- leptosSkill
- loreSkill
- lower-bound-reviewSkill
- macvlan-netSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 27
Read docs/CROSS-PROJECT-LESSONS-2026-09.md before making architectural changes.
- Very specific: line 33
Do not treat Copilot/Codex state as canonical project state.
- Distinctive: line 38
Before proposing architecture or cross-project primitives, read:
- Distinctive: line 44
Do not repeat research already indexed unless new evidence or requirements materially change the conclusion.
≈ “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
Role
Agent policy/workflow/skills layer.
Owns
- workflow guidance
- routing policy baselines
- agent skills/evals
Do not duplicate
- canonical runtime state
- filesystem version store
- lineage database
Sibling repos to consult first
- ryanmaclean/bop
- ryanmaclean/smolfire
- ryanmaclean/moth
Cross-project context
Read docs/CROSS-PROJECT-LESSONS-2026-09.md before making architectural changes.
Agent delegation
- Primary GitHub coding agent: Copilot when assignable/available.
- Fallback: delegate the issue or PR to Codex with
@codex. - Do not treat Copilot/Codex state as canonical project state; keep canonical work in repo issues/BOP/filesystem state.
Binding cross-project constraints
Before proposing architecture or cross-project primitives, read:
ryanmaclean/skills/docs/CONSTRAINTS.mdryanmaclean/skills/docs/RESEARCH-INDEX.md- this repo's
.project.toml
Do not repeat research already indexed unless new evidence or requirements materially change the conclusion.
New architecture proposals must identify:
- the invariant uniquely owned by the new layer
- why a lower existing layer cannot own it
- what duplicated state or layer the proposal removes
Key constraints include:
- visibility is not durability
- identity, order, content hash, and presentation remain distinct
- ordering has one source
- retries reuse logical operation identity
- queues/rings are transport, not semantics
- derived views are disposable
- push invariants down; pull policy up
- formalize durable primitives before RTL/FPGA
- RISC-V is optional control plane, not the v0 datapath
- ASIC requires measured FPGA justification
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.