agentleFS
Sign inStart free
UsmansayedUsmansayed/scubiee/AGENTS.md

scubiee

AGENTS.md145 starsChanged 7 days agoApache-2.0View on GitHub

LOCATE PRIORITY (managed): Soft/structural → Prefer Scubiee map over host explore-first (Task / codebase_search). Needles/names/paths → Prefer host Grep/Glob/Read (Forbid-first map). MUST Use Scubiee MCP for locate when @scubiee/* / MCP locate tools are callable. ONE tool map, config = find | focus (plus gate/status for health). How-to → Scubiee MCP server instructions every turn (this GATE is the duty to enter the ladder). Prefer host first (Forbid-first map): - Literals / imports / error strings / JWT-like / named-symbol…

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

    MUST Use Scubiee MCP for locate: when @scubiee/* / MCP locate tools are callable.

    line 6
  2. Very specific:

    After a map result → guided Grep/Read on the returned loc spans only.

    line 12
  3. Distinctive:

    Query quality (high ROI): write ~25–120 denser code-vocab tokens (target ≥40): concrete symbols, module paths, APIs, error strings, …

    line 15

≈ “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
<!-- scubiee:start -->

GATE 1:ce_b867ad869c948914bf7c8e8640a2a5e3 - Managed repo. project_id='ce_b867ad869c948914bf7c8e8640a2a5e3'.

LOCATE PRIORITY (managed): Soft/structural → Prefer Scubiee map over host explore-first (Task / codebase_search). Needles/names/paths → Prefer host Grep/Glob/Read (Forbid-first map).

MUST Use Scubiee MCP for locate when @scubiee/* / MCP locate tools are callable. ONE tool map, config = find | focus (plus gate/status for health). How-to → Scubiee MCP server instructions every turn (this GATE is the duty to enter the ladder).

Prefer host first (Forbid-first map):

  • Literals / imports / error strings / JWT-like / named-symbol under a known path → Grep.
  • Filenames → Glob; known path:lines → Read.
  • Health / readiness / warm_state / provider-dep errors → gate/status + Grep — not soft map.
  • After a map result → guided Grep/Read on the returned loc spans only; re-Grep of ground map already returned = FAIL.

WHEN SCUBIEE MCP IS AVAILABLE — pick ONE config, act, STOP:

  • Query quality (high ROI): write ~25–120 denser code-vocab tokens (target ≥40): concrete symbols, module paths, APIs, error strings, technologies, and outcome verbs — not a synonym/keyword dump. One tight sentence; BAN multi-paragraph queries and <25-token vibe queries. Vague one-liner or keyword-salad = FAIL.
  • Don't know where it is → map config=find query=<one specific target> → ranked locations + the top result's code inline. If that's the place, EDIT — don't re-view it. find also ORIENTS a wide/unknown area (broad query) and pulls code near a chunk you hold (put its names in the query).
  • Have a name, want it + its wiring → map config=focus names=[Sym] → that symbol's full code + callers/callees + sibling names in one unit. Edit from this; no follow-up. Known name → focus FIRST; don't fold a known-name lookup into a semantic find.
  • DECOMPOSE multi-target work: a task touching TWO distinct places is TWO calls, not one bundled query — a broad query mixing targets returns only the strongest and silently drops the other. Issue them separately.
  • Native-first while MCP is up = FAIL on soft/structural.
  • Native Grep/span-Read only after a map result's locs, or if Scubiee MCP is fully uncallable (no deadlock).
  • Empty/useless result or needle/health ask → stop the ladder; Grep/Read — do not stack map/status thrash.
  • Budget ≤3 locate calls/beat. BAN whole-file Read of result paths — Read only the returned loc spans.
  • Edit/Write stay native.
<!-- scubiee:end -->

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 repositoryOne other file 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.

Reviews can't be read right now.

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