agentleFS
Sign inStart free
search-atlas-groupsearch-atlas-group/amm-founding-circle/AGENTS.md

amm-founding-circle

AGENTS.md0 starsChanged 5 months agoMITView on GitHub

This repository is the canonical, single-root source for AMM skills, artifacts, tools, SHEP, and onboarding. These instructions apply to Codex, generic agents, and other CLI agents; Claude users should read CLAUDE.md, which points here. Resolve paths from these defaults (environment variables may override them): Keep personal/member files in work/; do not put them in the tracked founding-circle/ tree. Use migrate.sh or migrate.ps1 for legacy layouts. It is dry-run by default, writes a manifest, never deletes member files, and leaves 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:

    Keep personal/member files in work/.

    line 14
  2. Very specific:

    Use repository-relative paths when working inside this clone.

    line 19

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

Founding Circle agent instructions

This repository is the canonical, single-root source for AMM skills, artifacts, tools, SHEP, and onboarding. These instructions apply to Codex, generic agents, and other CLI agents; Claude users should read CLAUDE.md, which points here.

Resolve paths from these defaults (environment variables may override them):

  • AMM_MOTHERSHIP_ROOT: ~/amm-mothership (Windows: %USERPROFILE%\amm-mothership)
  • AMM_FOUNDING_CIRCLE_DIR: $AMM_MOTHERSHIP_ROOT/founding-circle
  • AMM_WORK_DIR: $AMM_MOTHERSHIP_ROOT/work
  • AMM_ARCHIVE_DIR: $AMM_MOTHERSHIP_ROOT/archive

Keep personal/member files in work/; do not put them in the tracked founding-circle/ tree. Use migrate.sh or migrate.ps1 for legacy layouts. It is dry-run by default, writes a manifest, never deletes member files, and leaves a temporary compatibility shim after --apply/-Apply.

Use repository-relative paths when working inside this clone. Do not create or update a sibling amm-toolkit; if one exists, report it and leave it untouched unless the member explicitly runs migration. Preserve local edits and never reset or force-update a dirty clone.

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