agentleFS
Sign inStart free
pschliekerpschlieker/getbacklane/AGENTS.md

getbacklane

AGENTS.md1 starsChanged 9 days agoMITView on GitHub

Guidance for coding agents working in this repo. .claude/CLAUDE.md points here. The public, agent-side half of Backlane: skills, setup guides and plugin manifests. The MCP server itself lives in a separate private repo and runs at https://app.getbacklane.com/mcp (tools: list_integrations, search, execute). - One skill per folder under skills/<name>/SKILL.md, with longer material in references/. - The MCP URL appears in .mcp.json, .cursor-plugin/plugin.json, gemini-extension.json, server.json, skills/backlane/references/setup.md and docs/setup/. Change all of them together. - Keep the version in .claude-plugin/plugin.json, .cursor-plugin/plugin.json, .codex-plugin/plugin.json, gemini-extension.json,…

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

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Keep the version in .claude-plugin/plugin.json, .cursor-plugin/plugin.json, .codex-plugin/plugin.json, gemini-extension.json, server.json …

    line 19
  2. Common:

    Never put credentials or customer data in this repo.

    line 31

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

Guidance for coding agents working in this repo. .claude/CLAUDE.md points here.

What this repo is

The public, agent-side half of Backlane: skills, setup guides and plugin manifests. The MCP server itself lives in a separate private repo and runs at https://app.getbacklane.com/mcp (tools: list_integrations, search, execute).

Conventions

  • One skill per folder under skills/<name>/SKILL.md, with longer material in references/.
  • The MCP URL appears in .mcp.json, .cursor-plugin/plugin.json, gemini-extension.json, server.json, skills/backlane/references/setup.md and docs/setup/. Change all of them together.
  • Keep the version in .claude-plugin/plugin.json, .cursor-plugin/plugin.json, .codex-plugin/plugin.json, gemini-extension.json, server.json and skills/backlane/SKILL.md in sync.
  • .codex-plugin/plugin.json is the ChatGPT/Codex manifest: listing copy, review test cases and the skills/get-started onboarding skill. Build the portal upload with npm run package:openai (writes dist/). Raise the version for every new upload.
  • server.json is the entry in the official MCP Registry (com.getbacklane/backlane). After changing it, republish with mcp-publisher validate && mcp-publisher publish. Publishing needs a DNS login for getbacklane.com (mcp-publisher login dns); the private key is kept outside this repo.
  • Never put credentials or customer data in this repo. It is public.
  • Setup instructions are maintained in packages/setup-guide/. The Markdown in docs/setup/ and skills/backlane/references/setup.md is generated; run npm run docs:generate after editing the shared source, then npm test and npm run docs:check. The app and website install this repo's main branch as @backlane/setup-guide and pick up changes on their next deploy, so keep the exported API in index.d.ts backwards compatible.

Testing a local edit

claude --plugin-dir .
claude plugin validate .

For Codex, add this repo as a local marketplace (.agents/plugins/marketplace.json):

codex plugin marketplace add .

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