agentleFS
Sign inStart free
nirholasnirholas/x402-suite/AGENTS.md

x402-suite

AGENTS.md4 starsChanged 22 days agoApache-2.0View on GitHub

Operating notes for AI coding agents (Claude Code, Codex, Cursor, Copilot and others) working in this repository. Everything here is derived from the files actually in the tree, so trust it over guesses, and update it when the facts change. Fifty open-source services that let AI agents buy real things - booking, travel, shopping, and the infrastructure underneath, priced per request over x402 No package manifest is checked in. Follow the installation steps in README.md. No build, test or lint…

  • Reads credentials

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    No package manifest is checked in.

    line 22
  2. Distinctive:

    No build, test or lint scripts are declared in the tree.

    line 26
  3. Very specific:

    Commit messages follow Conventional Commits (type(scope): summary), matching the existing history.

    line 31
  4. Distinctive:

    Read the surrounding code before adding to it, and match its naming, file organisation and error-handling style.

    line 32
  5. Distinctive:

    Keep README.md accurate: if a change alters behaviour, commands or configuration, update the docs in the same commit.

    line 33
  6. Distinctive:

    Do not leave TODO comments, stub functions, placeholder data or commented-out code behind.

    line 34

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

AGENTS.md

Operating notes for AI coding agents (Claude Code, Codex, Cursor, Copilot and others) working in this repository. Everything here is derived from the files actually in the tree, so trust it over guesses, and update it when the facts change.

What this repository is

Fifty open-source services that let AI agents buy real things - booking, travel, shopping, and the infrastructure underneath, priced per request over x402

Repository layout

  • docs/
  • README.md
  • LICENSE

Setup

No package manifest is checked in. Follow the installation steps in README.md.

Commands

No build, test or lint scripts are declared in the tree. Verify changes by running the project as README.md describes.

Conventions

  • .env files are gitignored; never commit credentials, and read configuration from environment variables.
  • Commit messages follow Conventional Commits (type(scope): summary), matching the existing history.
  • Read the surrounding code before adding to it, and match its naming, file organisation and error-handling style.
  • Keep README.md accurate: if a change alters behaviour, commands or configuration, update the docs in the same commit.
  • Do not leave TODO comments, stub functions, placeholder data or commented-out code behind. Finish what you start or leave it out.
  • Small, focused commits with a subject line that describes the change, not the act of committing.

Where to raise things

Download now (ZIP)

  • 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 28,693 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.

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