agentleFS
ainullmainullm/agent-checkpoint/adapters/AGENTS.md

agent-checkpoint / adapters

AGENTS.md3 starsChanged 39 days agoMITView on GitHub

  • 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 repository3 other files it gives its agents.

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When modifying, refactoring, or updating existing files in this workspace:

    line 5
  2. Very specific:

    Update sharded local index at .snapshots/<filepath>/manifest.json (< 40 tokens).

    line 10

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

AGENT-CHECKPOINT PROTOCOL v2.0 (Antigravity / Gemini CLI)

Add this section to your project's AGENTS.md or ~/.gemini/AGENTS.md

FILE MODIFICATION & AUDIT TRAIL PROTOCOL

When modifying, refactoring, or updating existing files in this workspace:

  1. BUCKETED PRE-EDIT SNAPSHOT: Before modifying any existing text, code, or document, copy its prior state to .snapshots/<filepath>/v<OLD_VERSION>.<ext>.
  2. SLIDING WINDOW RETENTION: Retain at most 5 latest snapshots per file bucket. Automatically prune older snapshots.
  3. IMPACT CLASSIFICATION: Classify change into MAJOR (architectural), MINOR (additive feature), or PATCH (bugfix/typo).
  4. TOKEN-OPTIMIZED DUAL-LEDGER:
    • Update sharded local index at .snapshots/<filepath>/manifest.json (< 40 tokens).
    • Append 1 line to REVISION_LOG.md using the compact Markdown table without reading historical logs.
  5. SAFETY EXCLUSIONS: Never snapshot heavy binary assets (models, datasets > 1 MB) or caches (node_modules, venv, __pycache__, .git).

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.