agentleFS
Sign inStart free
neoneyeneoneye/PlanExe/public/AGENTS.md

PlanExe

AGENTS.md402 starsChanged 3 months agoMITView on GitHub

Scope: static files under public/. Legacy compatibility endpoint: - https://mcp.planexe.org/llm.txt - This should remain an alias redirect to: https://mcp.planexe.org/llms.txt

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Distinctive:

    Keep exactly one source-of-truth file for this content.

    line 13
  2. Distinctive:

    Do not add near-duplicate copies such as:

    line 14
  3. Distinctive:

    If container packaging needs it, copy the canonical file at build time.

    line 30
  4. Distinctive:

    Do not fork content per service unless explicitly required.

    line 31
  5. Very specific:

    When updating agent-discovery text, edit only: public/llms.txt

    line 34

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

public agent instructions

Scope: static files under public/.

Purpose of llms.txt

  • llms.txt is PlanExe's AI-agent discovery metadata.
  • It explains what PlanExe does, how agents connect, and which endpoints/tools exist.
  • This file is product-level metadata, not service-specific metadata.

Canonical source

  • Canonical file path: public/llms.txt
  • Keep exactly one source-of-truth file for this content.
  • Do not add near-duplicate copies such as:
    • mcp_cloud/llms.txt
    • mcp_cloud/llm.txt
    • docs/llms.txt

Intended public endpoints

  • https://home.planexe.org/llms.txt
  • https://mcp.planexe.org/llms.txt

Legacy compatibility endpoint:

  • https://mcp.planexe.org/llm.txt
  • This should remain an alias redirect to: https://mcp.planexe.org/llms.txt

Implementation intent

  • mcp_cloud should serve /llms.txt from the canonical file in public/.
  • If container packaging needs it, copy the canonical file at build time.
  • Do not fork content per service unless explicitly required.

Change policy

  • When updating agent-discovery text, edit only: public/llms.txt
  • Then verify both endpoints still serve the same content:
    • https://home.planexe.org/llms.txt
    • https://mcp.planexe.org/llms.txt

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. PlanExeOrg/PlanExe★ 402100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 repository12 other files 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