agentleFS
Sign inStart free
GitHubKnown publishergithub/evals-action/AGENTS.md

evals-action

AGENTS.md0 starsChanged 26 days agoMITView on GitHub

- Keep this a thin GitHub adapter over the acquired Vally CLI. Translate supported commands and consume native JSONL; never duplicate selection, configuration parsing, grading or execution. - Use Node 24, the pinned pnpm version, and one lockfile. Install with scripts disabled. Run focused tests during development and pnpm check before review. - Rebuild and commit dist after source changes. Never manually edit bundles. - Do not run models, add credentials, publish, merge or change repository visibility without separate authorization.…

  • 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 repositoryOne other file it gives its agents.

The file

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

5 rules. About 2 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈2

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Keep this a thin GitHub adapter over the acquired Vally CLI.

    line 3
  2. Very specific:

    Use Node 24, the pinned pnpm version, and one lockfile.

    line 6
  3. Common:

    Do not run models, add credentials, publish, merge or change repository visibility without separate authorization.

    line 9
  4. Common:

    Treat prompts, source, raw evidence and credentials as private.

    line 13
  5. Very specific:

    Use argument-array process calls.

    line 15

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

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

Contributor instructions

  • Keep this a thin GitHub adapter over the acquired Vally CLI. Translate supported commands and consume native JSONL; never duplicate selection, configuration parsing, grading or execution.
  • Use Node 24, the pinned pnpm version, and one lockfile. Install with scripts disabled. Run focused tests during development and pnpm check before review.
  • Rebuild and commit dist after source changes. Never manually edit bundles.
  • Do not run models, add credentials, publish, merge or change repository visibility without separate authorization.
  • Preserve unknown counts and not-run outcomes. Never infer pass from process completion or use a report-only override for native failures.
  • Treat prompts, source, raw evidence and credentials as private. Default artifacts are allowlisted structured projections only.
  • Use argument-array process calls. Use actions/checkout@v7; keep other third-party Actions SHA-pinned.
  • Qualify native behavior with the built-in mock executor and deterministic graders. Do not substitute model-backed runs for model-free acceptance.

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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free