agentleFS
Sign inStart free
docxologydocxology/template/.github/actions/setup-ci-execution-user/AGENTS.md

template / setup-ci-execution-user

AGENTS.md20 starsChanged 13 days agoApache-2.0View on GitHub

This is a thin Linux-only setup action. Business logic and validation belong in infrastructure/core/testing/ciexecutionuser.py, with genuine controls in tests/infratests/core/testciexecutionuser.py. Prepare only after the caller's complete inputs and before custody. Require a fresh unprivileged account, coherent credentials, unchanged global process visibility, exact Git/source bytes and modes, and independent cache inodes before ownership changes. Never substitute an unreadable process for verified absence. Keep environment forwarding explicit and free of tokens or authentication configuration. Preserve original command arguments and exit status. Export only…

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep environment forwarding explicit and free of tokens or authentication configuration.

    line 12

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

Execution-account contract

This is a thin Linux-only setup action. Business logic and validation belong in infrastructure/core/testing/ci_execution_user.py, with genuine controls in tests/infra_tests/core/test_ci_execution_user.py.

Prepare only after the caller's complete inputs and before custody. Require a fresh unprivileged account, coherent credentials, unchanged global process visibility, exact Git/source bytes and modes, and independent cache inodes before ownership changes. Never substitute an unreadable process for verified absence.

Keep environment forwarding explicit and free of tokens or authentication configuration. Preserve original command arguments and exit status. Export only the byte-identical readiness evidence into the declared transport directory; keep original evidence permissions unchanged. Services started during preparation retain their existing ownership and identity-checked cleanup. Prune only Source-declared disposable pytest scratch; retain the bounded exclusion record and refuse unexpected links or special files in the remaining evidence.

Changes require actionlint, the focused genuine helper controls, independent review, and affected hosted Linux execution. Local static checks do not qualify user creation, credential transitions or the release producer.

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