agentleFS
everrunseverruns/everruns/plugins/AGENTS.md

everruns / plugins

AGENTS.md67 starsChanged 16 days agoMITView on GitHub

Plugins kept in this repository, one directory per plugin. First-party plugins for coding agents (the everruns plugin for Claude Code, Codex, Cursor and Gemini CLI) live in everruns/plugins, which is also the default marketplace every Everruns organization starts with. - The plugin name and version must match across the root plugin.json and all three host manifests (.claude-plugin/, .codex-plugin/, .cursor-plugin/). - The skill directory (skills/<name>/SKILL.md) must declare matching frontmatter name and description. - Do not add a root marketplace or a…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Do not add a root marketplace or a coding-agent plugin here.

    line 20
  2. Very specific:

    Run bash scripts/test-plugins.sh.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Plugins

Plugins kept in this repository, one directory per plugin. First-party plugins for coding agents (the everruns plugin for Claude Code, Codex, Cursor and Gemini CLI) live in everruns/plugins, which is also the default marketplace every Everruns organization starts with.

Layout

DirectoryPluginHosts
plugins/resend/resend: send email via Resend over MCP (skills/resend/)Everruns (inbound fixture and example), Claude, Codex, Cursor

Rules

  • The plugin name and version must match across the root plugin.json and all three host manifests (.claude-plugin/, .codex-plugin/, .cursor-plugin/).
  • The skill directory (skills/<name>/SKILL.md) must declare matching frontmatter name and description.
  • Do not add a root marketplace or a coding-agent plugin here; add it to everruns/plugins.

Verification

Run bash scripts/test-plugins.sh. See knowledge/integrations/plugins.md for the plugin contract.

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.