dogma / {{cookiecutter.project_slug}}
AGENTS.md2 starsChanged 8 months agoApache-2.0View on GitHub
This repository is a fork of EndogenAI/dogma. See the upstream AGENTS.md for full operational constraints and guiding axioms. When you run the adoption wizard it copies a full AGENTS.md into this directory — replace this notice once that step is complete. This fork specializes dogma's Core Layer axioms for {{ cookiecutter.project_name }}. Before any first action, agents must read client-values.yml — the Deployment Layer file that encodes this project's mission, priorities, and axiom emphasis. Deployment Layer constraints may not override…
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,542 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 repository27 other files it gives its agents.
- adopt-test-2/AGENTS.mdAGENTS.md
- adopt-test-3/AGENTS.mdAGENTS.md
- adopt-test/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- .github/agents/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-file-authoringSkill
- conventional-commitSkill
- corpus-sweepSkill
- deep-research-sprintSkill
- delegation-routingSkill
- phase-gate-sequenceSkill
- prompt-archaeologySkill
- pr-review-replySkill
- pr-review-triageSkill
- rate-limit-resilienceSkill
- research-epic-planningSkill
- secondary-research-sprintSkill
- session-managementSkill
- session-retrospectiveSkill
- skill-authoringSkill
- source-cachingSkill
- sprint-planningSkill
- transcript-extractionSkill
- validate-before-commitSkill
- workplan-scaffoldSkill
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 12
Before any first action, agents must read client-values.yml — the Deployment Layer file that encodes this project's mission, priorities, …
≈ “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 — Deployment Layer Governance Notice
This repository is a fork of EndogenAI/dogma.
See the upstream AGENTS.md for full
operational constraints and guiding axioms. When you run the adoption wizard it copies a
full AGENTS.md into this directory — replace this notice once that step is complete.
Deployment Layer
This fork specializes dogma's Core Layer axioms for {{ cookiecutter.project_name }}.
Before any first action, agents must read client-values.yml — the Deployment Layer
file that encodes this project's mission, priorities, and axiom emphasis.
Deployment Layer constraints may not override MANIFESTO.md Core Layer constraints (Endogenous-First, Algorithms Before Tokens, Local Compute-First). They may only specialize or add priorities.
Quickstart
# Install dependencies
uv sync
# Install pre-commit hooks
uv run pre-commit install
uv run pre-commit install --hook-type pre-push
# Run validation
uv run pre-commit run --all-files
uv run pytest tests/ -m "not slow and not integration" -qUpstream governance
To pull in upstream dogma governance improvements:
git remote add dogma https://github.com/EndogenAI/dogma.git
git fetch dogmaRefer to the upstream Product Fork Initialization Guide for the full initialization and sync workflow.
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.

