agentleFS
Sign inStart free
jscraikjscraik/Agent-Skills/Wiki/AGENTS.md

Agent-Skills / Wiki

AGENTS.md9 starsChanged 46 days agoApache-2.0View on GitHub

- Treat this subtree as reference, knowledge, and wiki material unless a file is explicitly admitted by a plan, policy, or workflow as binding source. - Preserve provenance, dates, source links, and migration notes when editing knowledge pages. - Do not let wiki prose override AGENTS.md, Docs/agents/**, schemas, validators, or executable contracts. Promote durable rules into the owning instruction or policy surface instead. - Validate internal links and any generated index that consumes the wiki. - If a wiki page…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Treat this subtree as reference, knowledge, and wiki material unless a file is explicitly admitted by a plan, policy, or workflow as …

    line 14
  2. Very specific:

    Do not let wiki prose override AGENTS.md, Docs/agents/, schemas, validators, or executable contracts.

    line 18
  3. Distinctive:

    If a wiki page is used as evidence for a code or governance change, cite the owning source of truth as well as the wiki summary.

    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

Wiki Agent Guide

Scope

  • Applies to Wiki/**.
  • Inherits the repository root AGENTS.md.

Edit Policy

  • Treat this subtree as reference, knowledge, and wiki material unless a file is explicitly admitted by a plan, policy, or workflow as binding source.
  • Preserve provenance, dates, source links, and migration notes when editing knowledge pages.
  • Do not let wiki prose override AGENTS.md, Docs/agents/**, schemas, validators, or executable contracts. Promote durable rules into the owning instruction or policy surface instead.

Context Pointers

  • Wiki entrypoint: README.md.
  • Published/wiki pages: Wiki/wiki/**.
  • Workflow and safety guidance: ../Docs/agents/13-workflow-and-safety-guidance.md.

Validation

  • Validate internal links and any generated index that consumes the wiki.
  • If a wiki page is used as evidence for a code or governance change, cite the owning source of truth as well as the wiki summary.

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