agentleFS
Sign inStart free
Anil-matchaAnil-matcha/open-dots/AGENTS.md

open-dots

AGENTS.md6.9k starsChanged 7 days agoApache-2.0View on GitHub

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about Anil-matcha/open-dots

The biggest 5 of 15 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 15

Talked about on GitHub and Hacker News (15 times).

On GitHub · 14

9 more on GitHub

On Hacker News · 1

  • 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,774 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

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run independent backend and frontend checks in parallel when they cover the same change.

    line 6
  2. Very specific:

    Use the backend SQLite and throwaway TOKEN_ENCRYPTION_KEYS values from .github/workflows/ci.yml.

    line 8
  3. Very specific:

    Read a package-level AGENTS.md before changing files in that package.

    line 14

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

Repository Agent Instructions

Test workflow

  • For a narrow change, run the smallest tests that cover the changed behavior first. Find test commands in the relevant package and CI workflow; avoid running the entire backend suite as the default local check.
  • Run independent backend and frontend checks in parallel when they cover the same change. For a failure, rerun the specific failing test after fixing it.
  • The full backend suite includes process, socket, and end-to-end tests and takes several minutes. Run it for broad backend changes, when requested, or as part of CI/release verification. Do not weaken or remove CI coverage to make local iteration faster.
  • Use the backend SQLite and throwaway TOKEN_ENCRYPTION_KEYS values from .github/workflows/ci.yml; never use production credentials in tests.
  • Some integration tests need process or localhost socket permissions that a restricted environment may deny. Treat those as environment failures, not product failures, and rerun them in an environment that supports them when the result matters.
  • Report exactly which checks passed, skipped, failed, or were interrupted. An incomplete run is not a passing full suite.

Local package instructions

  • Read a package-level AGENTS.md before changing files in that package. For example, frontend/AGENTS.md contains the frontend-specific framework rules.

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