amm-founding-circle
AGENTS.md0 starsChanged 5 months agoMITView on GitHub
This repo is for Agentic Marketing Mastermind members. Keep it teaching-first, and clearly label any advanced source material that needs local adaptation. - Do not add employee-only deployment systems, unpublished customer data, credentials, or token locations. - Prefer examples that work against public tools, local files, GitHub-style pull requests, pasted transcripts, or clearly documented optional services. - Keep commands safe to run on a member laptop. If a command changes files, make the affected path explicit. - Never commit real…
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 repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- shep/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- shep/CLAUDE.mdCLAUDE.md
- advisory-version-checkSkill
- aeo-llm-content-plannerSkill
- agency-command-centerSkill
- agency-morning-briefSkill
- agency-scorecardSkill
- agent-runbookSkill
- agent-usageSkill
- autonomy-budgetSkill
- backlink-pr-angle-generatorSkill
- brand-kit-from-urlSkill
- browser-automationSkill
- building-autonomous-agentsSkill
- capability-mapSkill
- case-study-engineSkill
- clickup-apiSkill
- client-dashboardSkill
- client-health-scoreSkill
- client-onboarding-osSkill
- cli-llm-routingSkill
- codebase-mapSkill
- command-from-your-phoneSkill
- competitor-content-gap-analysisSkill
- connection-monitorSkill
- content-brief-generatorSkill
- determinism-patternSkill
- dispatch-and-briefSkill
- division-operating-modelSkill
- dreamingSkill
- durable-stateSkill
- entity-topical-authority-mapperSkill
- first-real-jobSkill
- founding-circle-ai-securitySkill
- gbp-competitor-auditSkill
- goal-modeSkill
- host-your-agentSkill
- html-reportsSkill
- instinct-bridgeSkill
- evolveSkill
- learn-evalSkill
- learnSkill
- promoteSkill
- skill-createSkill
- internal-linking-auditorSkill
- keyword-deep-diveSkill
- ladder-auditSkill
- lanes-momentum-frameworkSkill
- launch-websiteSkill
- llm-citation-auditSkill
- migration-seo-paritySkill
- migration-visual-checkSkill
- model-gear-routerSkill
- multi-account-gatewaySkill
- multi-model-councilSkill
- night-shiftSkill
- novaSkill
- per-client-memory-routerSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 1 is common, 5 are distinctive, and 0 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Do not add employee-only deployment systems, unpublished customer data, credentials, or token locations.
- Distinctive: line 10
Prefer examples that work against public tools, local files, GitHub-style pull requests, pasted transcripts, or clearly documented optional …
- Distinctive: line 12
Keep commands safe to run on a member laptop.
- Distinctive: line 14
Never commit real tokens, cookies, browser profiles, session dumps, or member data.
- Distinctive: line 19
Prefer concrete playbooks over theory.
- Distinctive: line 21
Keep advanced orchestration concepts as optional patterns, not prerequisites.
≈ “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.
Files
Repository Instructions
This repo is for Agentic Marketing Mastermind members. Keep it teaching-first, and clearly label any advanced source material that needs local adaptation.
Content Boundary
- Do not add employee-only deployment systems, unpublished customer data, credentials, or token locations.
- Prefer examples that work against public tools, local files, GitHub-style pull requests, pasted transcripts, or clearly documented optional services.
- Keep commands safe to run on a member laptop. If a command changes files, make the affected path explicit.
- Never commit real tokens, cookies, browser profiles, session dumps, or member data.
Tone
- Prefer concrete playbooks over theory.
- Explain why a rule exists before giving commands.
- Keep advanced orchestration concepts as optional patterns, not prerequisites.
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
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.