agentleFS
Sign inStart free
anvitnaikanvitnaik/free-claude-code/AGENTS.md

free-claude-code

AGENTS.md1 starsChanged 7 months agoMITView on GitHub

This file is identical to CLAUDE.md. Keep them in sync.

  • Pipes a download into a shell
  • Reads credentials

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

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

Show its rules and text

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

19 rules. About 0 are common, 6 are distinctive, and 13 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 13

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always use uv run to run files instead of the global python command.

    line 9
  2. Very specific:

    Read .env.example for environment variables.

    line 11
  3. Distinctive:

    All CI checks must pass; failing checks block merge.

    line 12
  4. Very specific:

    Add tests for new changes (including edge cases), then run uv run pytest.

    line 13
  5. Very specific:

    Run checks in this order: uv run ruff format, uv run ruff check, uv run ty check, uv run pytest.

    line 14
  6. Very specific:

    Do not add # type: ignore or # ty: ignore.

    line 15
  7. Very specific:

    All 5 checks are enforced in tests.yml on push/merge.

    line 16
  8. Very specific:

    Shared utilities: Put shared Anthropic protocol logic in neutral core/anthropic/ modules.

    line 26
  9. Very specific:

    Encapsulation: Use accessor methods for internal state (e.g.

    line 28
  10. Very specific:

    Provider-specific config: Keep provider-specific fields (e.g.

    line 29
  11. Very specific:

    Dead code: Remove unused code, legacy systems, and hardcoded values.

    line 30
  12. Very specific:

    Performance: Use list accumulation for strings (not += in loops), cache env vars at init, prefer iterative over recursive when stack depth …

    line 31
  13. Very specific:

    Platform-agnostic naming: Use generic names (e.g. PLATFORM_EDIT) not platform-specific ones (e.g.

    line 32
  14. Very specific:

    No type ignores: Do not add # type: ignore or # ty: ignore.

    line 33
  15. Distinctive:

    Complete migrations: When moving modules, update imports to the new owner and remove old compatibility shims in the same change unless …

    line 34
  16. Distinctive:

    ANALYZE: Read relevant files. Do not guess.

    line 39
  17. Distinctive:

    VERIFY: Run ci checks and relevant smoke tests.

    line 42
  18. Distinctive:

    SPECIFICITY: Do exactly as much as asked.

    line 43
  19. Distinctive:

    Prefer built-in tools (grep, read_file, etc.) over manual workflows.

    line 53

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

AGENTIC DIRECTIVE

This file is identical to CLAUDE.md. Keep them in sync.

CODING ENVIRONMENT

  • Install astral uv using "curl -LsSf https://astral.sh/uv/install.sh | sh" if not already installed and if already installed then update it to the latest version
  • Install Python 3.14 using uv python install 3.14 if not already installed
  • Always use uv run to run files instead of the global python command.
  • Current uv ruff formatter is set to py314 which has supports multiple exception types without paranthesis (except TypeError, ValueError:)
  • Read .env.example for environment variables.
  • All CI checks must pass; failing checks block merge.
  • Add tests for new changes (including edge cases), then run uv run pytest.
  • Run checks in this order: uv run ruff format, uv run ruff check, uv run ty check, uv run pytest.
  • Do not add # type: ignore or # ty: ignore; fix the underlying type issue.
  • All 5 checks are enforced in tests.yml on push/merge.

IDENTITY & CONTEXT

  • You are an expert Software Architect and Systems Engineer.
  • Goal: Zero-defect, root-cause-oriented engineering for bugs; test-driven engineering for new features. Think carefully; no need to rush.
  • Code: Write the simplest code possible. Keep the codebase minimal and modular.

ARCHITECTURE PRINCIPLES (see PLAN.md)

  • Shared utilities: Put shared Anthropic protocol logic in neutral core/anthropic/ modules. Do not have one provider import from another provider's utils.
  • DRY: Extract shared base classes to eliminate duplication. Prefer composition over copy-paste.
  • Encapsulation: Use accessor methods for internal state (e.g. set_current_task()), not direct _attribute assignment from outside.
  • Provider-specific config: Keep provider-specific fields (e.g. nim_settings) in provider constructors, not in the base ProviderConfig.
  • Dead code: Remove unused code, legacy systems, and hardcoded values. Use settings/config instead of literals (e.g. settings.provider_type not "nvidia_nim").
  • Performance: Use list accumulation for strings (not += in loops), cache env vars at init, prefer iterative over recursive when stack depth matters.
  • Platform-agnostic naming: Use generic names (e.g. PLATFORM_EDIT) not platform-specific ones (e.g. TELEGRAM_EDIT) in shared code.
  • No type ignores: Do not add # type: ignore or # ty: ignore. Fix the underlying type issue.
  • Complete migrations: When moving modules, update imports to the new owner and remove old compatibility shims in the same change unless preserving a published interface is explicitly required.
  • Maximum Test Coverage: There should be maximum test coverage for everything, preferably live smoke test coverage to catch bugs early

COGNITIVE WORKFLOW

  1. ANALYZE: Read relevant files. Do not guess.
  2. PLAN: Map out the logic. Identify root cause or required changes. Order changes by dependency.
  3. EXECUTE: Fix the cause, not the symptom. Execute incrementally with clear commits.
  4. VERIFY: Run ci checks and relevant smoke tests. Confirm the fix via logs or output.
  5. SPECIFICITY: Do exactly as much as asked; nothing more, nothing less.
  6. PROPAGATION: Changes impact multiple files; propagate updates correctly.

SUMMARY STANDARDS

  • Summaries must be technical and granular.
  • Include: [Files Changed], [Logic Altered], [Verification Method], [Residual Risks] (if no residual risks then say none).

TOOLS

  • Prefer built-in tools (grep, read_file, etc.) over manual workflows. Check tool availability before use.

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