agentleFS
srednoff888-artsrednoff888-art/srednoff-os-for-claude/AGENTS.md

srednoff-os-for-claude

AGENTS.md1 starsChanged 5 months agoMITView on GitHub

This repository is primarily configured for Claude Code through CLAUDE.md. If you are another coding agent (Codex, Cursor, Gemini, etc.), follow the same core rules: Main instruction file:

  • 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 33,315 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 repository6 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you are another coding agent (Codex, Cursor, Gemini, etc.), follow the same core rules:

    line 5
  2. Very specific:

    use .agent/ workflow files.

    line 8
  3. Very specific:

    use .claude/rules/ as modular rules.

    line 9
  4. Distinctive:

    ask at most 5 blocking questions.

    line 11
  5. Distinctive:

    do not overwrite existing work.

    line 12
  6. Distinctive:

    do not perform destructive actions without explicit user approval.

    line 13
  7. Very specific:

    run tests/build/lint before final response when possible.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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 — Agent Interop Instructions

This repository is primarily configured for Claude Code through CLAUDE.md.

If you are another coding agent (Codex, Cursor, Gemini, etc.), follow the same core rules:

  • read CLAUDE.md;
  • use .agent/ workflow files;
  • use .claude/rules/ as modular rules;
  • perform GitHub research before non-trivial work;
  • ask at most 5 blocking questions;
  • do not overwrite existing work;
  • do not perform destructive actions without explicit user approval;
  • run tests/build/lint before final response when possible.

Main instruction file:

@CLAUDE.md

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.