agentleFS
Sign inStart free
docxologydocxology/template/.github/actions/setup-acceptance-model/AGENTS.md

template / setup-acceptance-model

AGENTS.md20 starsChanged 2 months agoApache-2.0View on GitHub

This composite action only orchestrates preparation of one pinned local model and its owned daemon. 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 cache contains only the fixed manifest and model blobs. Cache hits never bypass byte-length, SHA-256 or regular-file checks; corrupt or symlinked entries fail before daemon startup rather than being replaced.…

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
  1. Very specific:

    Do not call it on a shared workstation.

    line 4
  2. Very specific:

    Every caller of that action must perform identity-checked process-group cleanup in an always() step.

    line 15
  3. Very specific:

    Run actionlint after edits and retain genuine failed preparation diagnostics.

    line 18

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

setup-acceptance-model contract

This composite action only orchestrates preparation of one pinned local model and its owned daemon. 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 cache contains only the fixed manifest and model blobs. Cache hits never bypass byte-length, SHA-256 or regular-file checks; corrupt or symlinked entries fail before daemon startup rather than being replaced. Runtime/daemon custody and inference records always remain in the fresh owned directory.

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.

Run actionlint after edits and retain genuine failed preparation diagnostics. See README.md for usage.

An owned supervisor remains the process-group anchor throughout observation, including when the server or its first runner exits. It ignores SIGTERM so cleanup retains a verified owner until the final whole-group SIGKILL and live member readback. Cleanup authenticates PID/birth identities and refuses reuse.

Download now (ZIP)

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.

Check your setup, free