agentleFS
Sign inStart free
jsleemasterjsleemaster/gooblin/AGENTS.md

gooblin

AGENTS.md3 starsChanged 5 months agoMITView on GitHub

Use Gooblin principles when working in this repository. When editing a skill, preserve: If a behavior rule changes, update or add an example and consider whether evals/rubric.md needs a matching criterion. Every change should respect the shared kernel: Never simplify away: Plugin files and hooks must remain safe by default:

  • 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 repository8 other files it gives its agents.

The file

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

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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 Gooblin principles when working in this repository.

    line 3
  2. Distinctive:

    Prefer small, safe, verified documentation changes.

    line 8
  3. Distinctive:

    Do not add app scaffolding, build tooling, bundlers, frameworks, or runtime services unless explicitly requested.

    line 9
  4. Distinctive:

    Do not add dependencies without a concrete distribution or compatibility reason.

    line 10
  5. Distinctive:

    Keep package metadata minimal and distribution-focused.

    line 11
  6. Distinctive:

    Never fake adoption, benchmarks, citations, integrations, marketplace approval, or test results.

    line 12
  7. Distinctive:

    When editing a skill, preserve:

    line 16
  8. Very specific:

    If a behavior rule changes, update or add an example and consider whether evals/rubric.md needs a matching criterion.

    line 25
  9. Distinctive:

    Every change should respect the shared kernel:

    line 29
  10. Distinctive:

    No automatic mutation of user files.

    line 60
  11. Distinctive:

    No noisy failures when plugin environments are unavailable.

    line 61

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

AGENTS.md

Use Gooblin principles when working in this repository.

Repository Rules

  • This repository is a plugin-style Agent Skills pack, not an app or runtime.
  • Prefer small, safe, verified documentation changes.
  • Do not add app scaffolding, build tooling, bundlers, frameworks, or runtime services unless explicitly requested.
  • Do not add dependencies without a concrete distribution or compatibility reason.
  • Keep package metadata minimal and distribution-focused.
  • Never fake adoption, benchmarks, citations, integrations, marketplace approval, or test results.

Editing Skills

When editing a skill, preserve:

  • Role.
  • Trigger/use cases.
  • Workflow.
  • Output template.
  • Safety floor.
  • Verification requirement.

If a behavior rule changes, update or add an example and consider whether evals/rubric.md needs a matching criterion.

Gooblin Kernel

Every change should respect the shared kernel:

  1. Spec first.
  2. Plan before code unless the change is trivial.
  3. Smallest safe change.
  4. TDD or examples when behavior changes.
  5. Review before final.
  6. Verification required.
  7. Safety floor stays intact.
  8. Learning ledger changes require maintainer review.

Safety Floor

Never simplify away:

  • Auth/authz.
  • Input validation.
  • Secrets handling.
  • Data loss prevention.
  • Migration rollback.
  • Accessibility basics.
  • User-stated constraints.
  • Production safety.

Distribution Discipline

Plugin files and hooks must remain safe by default:

  • No network access.
  • No telemetry.
  • No dangerous commands.
  • No automatic mutation of user files.
  • No noisy failures when plugin environments are unavailable.

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