agentleFS
ZarKZarK/ai-supply-chain-guard/AGENTS.md

ai-supply-chain-guard

AGENTS.md14 starsChanged 39 days agoMITView on GitHub

Before any install, update, scaffold, package-manager command, CI action/workflow change, IDE/MCP/agent-tool change, release job, or dependency-provided tool execution, read and follow supply-chain-guard/SKILL.md. For deeper guidance, load only the relevant file from supply-chain-guard/references/. This repository is itself an Agent Skill package. Keep the installable skill folder portable: SKILL.md at the skill root, concise frontmatter, and optional supporting files under references/. Do not inject agent, model, tool, vendor, provider, or session attribution into public repository metadata or communication.

  • 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 32,671 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

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

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

    Before any install, update, scaffold, package-manager command, CI action/workflow change, IDE/MCP/agent-tool change, release job, or …

    line 3
  2. Distinctive:

    Do not inject agent, model, tool, vendor, provider, or session attribution into public repository metadata or communication.

    line 11
  3. Distinctive:

    Commit subjects and bodies must describe the change and rationale only.

    line 14
  4. Distinctive:

    Before creating or updating any public branch, commit, pull request, issue, comment, release, or tag, scan the proposed text for accidental …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Supply Chain Guard

Before any install, update, scaffold, package-manager command, CI action/workflow change, IDE/MCP/agent-tool change, release job, or dependency-provided tool execution, read and follow supply-chain-guard/SKILL.md.

For deeper guidance, load only the relevant file from supply-chain-guard/references/.

This repository is itself an Agent Skill package. Keep the installable skill folder portable: SKILL.md at the skill root, concise frontmatter, and optional supporting files under references/.

Public Metadata Hygiene

Do not inject agent, model, tool, vendor, provider, or session attribution into public repository metadata or communication.

  • Branch names must be neutral topic names. Do not use agent/tool prefixes or provider branding.
  • Commit subjects and bodies must describe the change and rationale only. Do not add generated-by, assisted-by, co-authored-by, signed-off-by, session IDs, local paths, transcript references, or vendor/tool attribution unless the maintainer explicitly requires that exact trailer.
  • Pull request and issue titles, bodies, comments, labels, milestones, release notes, changelogs, and review replies must be maintainer-centered and free of agent/tool/vendor/provider branding.
  • Before creating or updating any public branch, commit, pull request, issue, comment, release, or tag, scan the proposed text for accidental attribution, local context, hidden prompts, or tool-specific process narration.

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.