template / setup-acceptance-documents
AGENTS.md20 starsChanged 2 months agoApache-2.0View on GitHub
This composite action only orchestrates preparation of official document prerequisites. Do not call it on a shared workstation. It uses fresh RUNNER_TEMP storage and the disposable hosted runner's user font/tool directories. Third-party archives and model blobs must retain their exact source-pinned hashes and lengths. The model action binds an unoccupied loopback port, disables cloud operations and implicit model acquisition, and records its owned daemon PID and birth. Every caller of that action must perform identity-checked process-group cleanup in an always()…
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 4
Do not call it on a shared workstation.
- Very specific: line 10
Every caller of that action must perform identity-checked process-group cleanup in an always() step.
- Very specific: line 24
Run actionlint after edits and retain genuine failed preparation diagnostics.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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
setup-acceptance-documents contract
This composite action only orchestrates preparation of official document prerequisites.
Do not call it on a shared workstation. It uses fresh RUNNER_TEMP storage
and the disposable hosted runner's user font/tool directories. Third-party
archives and model blobs must retain their exact source-pinned hashes and lengths.
The model action binds an unoccupied loopback port, disables cloud operations
and implicit model acquisition, and records its owned daemon PID and birth.
Every caller of that action must perform identity-checked process-group cleanup
in an always() step. No shared service may be stopped or replaced.
mode defaults to native. Validate exactly native or converter before
cache restoration, download or setup. Pandoc/crossref verification is
unconditional; native package and JuliaMono preparation are conditioned only on
that validated output. All infrastructure and genuine acceptance callers use
native preparation. Ordinary project cells explicitly select native for EDA and
converter elsewhere, according to their actual source-declared tests.
Cache only official archives, with OS, architecture, validated mode and source identity in the key. Validate exact length and SHA-256 again before every use; cached data cannot supply test outcomes or acceptance.
Run actionlint after edits and retain genuine failed preparation diagnostics.
See README.md for usage.
Native callers must first prepare their selected locked Python environment.
python-executable defaults to .venv/bin/python; common acceptance explicitly
selects its prepared output/runtime-envs/3.14/bin/python. The helper's
--prepared-python PATH mode preserves that environment, checks actual CPython
support, and runs the unchanged LaTeX package validator with it. It performs no
Python bootstrap, dependency sync or implicit reconciliation. Missing runtime,
native tools, packages or failed validation remain failures.
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 28,693 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 repository42 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- fonds/AGENTS.mdAGENTS.md
- .github/actions/AGENTS.mdAGENTS.md
- .github/actions/setup-acceptance-fixtures/AGENTS.mdAGENTS.md
- .github/actions/setup-acceptance-model/AGENTS.mdAGENTS.md
- .github/actions/setup-docs-lint/AGENTS.mdAGENTS.md
- .github/actions/setup-native-installed-readiness/AGENTS.mdAGENTS.md
- .github/actions/setup-python-env/AGENTS.mdAGENTS.md
- .github/actions/upload-readiness-shards/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/ISSUE_TEMPLATE/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- infrastructure/AGENTS.mdAGENTS.md
- projects/AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- tools/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- advanced-evaluationSkill
- bdi-mental-statesSkill
- context-compressionSkill
- context-degradationSkill
- context-fundamentalsSkill
- context-optimizationSkill
- evaluationSkill
- filesystem-contextSkill
- harness-engineeringSkill
- hosted-agentsSkill
- latent-briefingSkill
- long-horizon-promptingSkill
- memory-systemsSkill
- multi-agent-patternsSkill
- project-developmentSkill
- self-improvement-loopsSkill
- tool-designSkill
- continual-learningSkill
- gauss-open-gauss-cliSkill
- infrastructure-overviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

