agentleFS
Sign inStart free
poweruserzpoweruserz/OpenTokenUsage/AGENTS.md

OpenTokenUsage

AGENTS.md37 starsChanged 8 months 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 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 repository7 other files it gives its agents.

The file

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

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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. Very specific:

    Use trash for deletes

    line 9
  2. Very specific:

    Use mv / cp to move and copy files

    line 10
  3. Distinctive:

    NEVER delete files, folders or other data unless explicilty approved or part of a plan

    line 15
  4. Distinctive:

    Before writing code, stricly follow the below research rules

    line 16
  5. Distinctive:

    Prefer skills if available over research.

    line 20
  6. Distinctive:

    Prefer researched knowledge over existing knowledge when skills are unavailable.

    line 21
  7. Distinctive:

    Before creating a PR or pushing to main, ensure that README.md is updated with what plugins are supported.

    line 31
  8. Distinctive:

    If the PR includes visual changes, refuse to create it without providing before/after screenshots.

    line 35
  9. Distinctive:

    Use below list to store and recall user notes when asked to do so.

    line 38
  10. Distinctive:

    Use this list when asked to remember things.

    line 40

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

OpenUsage

Instructions

  • CRITICAL: Use simple, concise language. Avoid overtechnical jargon.
  • Be radically precise. No fluff. Pure information only (drop grammar; min tokens).
  • Critical: DO NOT OVER-ENGINEER! This app is typically used by 2-5 people, internally only.

Guardrails

  • Use trash for deletes
  • Use mv / cp to move and copy files
  • Bugs: add regression test when it fits
  • A self-contained new feature gets its own module/component. Existing large files (src/lib/settings.ts, src/pages/settings.tsx, src/components/provider-card.tsx) are not split as part of a feature change; splitting one is its own change
  • Simplicity first: handle only important cases; no enterprise over-engineering/fallbacks
  • New functionality: small OR absolutely necessary
  • NEVER delete files, folders or other data unless explicilty approved or part of a plan
  • Before writing code, stricly follow the below research rules
  • User-facing text added/changed → translate it in all 11 languages (src/locales/*.ts, src/locales/plugin-errors/*.ts) in the same change, then bun run locales:lock. Never re-lock without translating.

Research

  • Prefer skills if available over research.
  • Prefer researched knowledge over existing knowledge when skills are unavailable.
  • Research: Exa to websearch early, and Ref to seek specific documention or web fetch.
  • Best results: Quote exact errors; prefer 2025-2026+ sources.

Error Handling

  • Expected issues: explicit result types (not throw/try/catch).
  • Unexpected issues: fail LOUD (throw/console.error); NEVER add silent fallbacks. Show the failure where the user acted when there is a place for it (an inline message, the card's error). The app has no toast system: don't call toast.error.
  • A failed settings save is logged with console.error only, the same for every setting; a visible save error would be one app-wide change, not part of a feature PR.

Before Creating Pull Request

  • Before creating a PR or pushing to main, ensure that README.md is updated with what plugins are supported.
  • On any plugin change/new plugin, audit plugin-exposed request/response fields against src-tauri/src/plugin_engine/host_api.rs redaction lists and add/update tests for gaps. Compare with existing plugins for patterns.
  • In plugin.json, set brandColor to the provider's real brand color.
  • Plugin SVG logos must use currentColor so icon theming works correctly.
  • If the PR includes visual changes, refuse to create it without providing before/after screenshots.

Project Memories

Use below list to store and recall user notes when asked to do so.

  • Use this list when asked to remember things. Keep each list item concise.
  • Tauri IPC: JS must use camelCase ({ batchId, pluginIds }), Tauri auto-converts to Rust's snake_case. Never send snake_case from JS—params silently won't match.
  • tauri-action latest.json: Parallel matrix builds are safe—action fetches existing latest.json, merges platform entries, re-uploads. No max-parallel: 1 needed.

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