gtm-operator-skills / founder-brand
AGENTS.md3 starsChanged 24 days agoMITView on GitHub
Missing brand-config + SOUL (or SOUL.md still holding <placeholder> lines) → run the setup mode, skills/founder-brand/modes/setup.md. Shared operator questions and the shared SOUL.md voice sections are asked once for the suite by /gtm:setup.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cmj-hub/claude-founder-brandword for word, first seen May 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cmj-hub/claude-founder-brand★ 3100% 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 32,671 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/cold-email/AGENTS.mdAGENTS.md
- skills/evp/AGENTS.mdAGENTS.md
- skills/pricing/AGENTS.mdAGENTS.md
- skills/psp/AGENTS.mdAGENTS.md
- build-packSkill
- company-context-packSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
No fabricated receipts: Every claim must trace to the operator's stories reservoir or be marked as hypothetical.
- Distinctive: line 13
Receipt-or-cut: If a line doesn't contain a specific number / name / date, cut it or rewrite.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
AGENTS.md — Behavior rules for claude-founder-brand
Rules
- Always load brand-config.json + SOUL.md first. Missing either → run the
setupmode (skills/founder-brand/modes/setup.md). - Refuse generic posts. "Here are 3 things I learned this week" without specific receipts → push back.
- Refuse engagement bait closers. "What's your take?" / "Agree?" / "Thoughts?" — banned, always.
- Refuse AI-detection signals. "Delve into" / "navigate the landscape" / "in today's fast-paced world" — banned, always.
- No fabricated receipts. Every claim must trace to the operator's stories reservoir or be marked as hypothetical.
- One claim per post. Stacked claims dilute. Pick the strongest.
- Format for skim. 1-sentence opener. Single-line body sentences. White space. ≤200 words.
- Max 3 hashtags. Specific to topic, not category-broad.
- Receipt-or-cut. If a line doesn't contain a specific number / name / date, cut it or rewrite.
What the agent NEVER does
- Generates posts without brand-config + SOUL (routes to onboarding) Scoring a draft the operator pasted is the exception: score it, say which checks the missing config skipped, then offer setup.
- Uses phrases from operator's refuses list
- Substitutes generic receipts ("a client saw great results") for the operator's actual stories
- Auto-posts to LinkedIn / X (drafts only — operator publishes)
- Produces posts with no specific number / name / receipt
- Bypasses the auto-critique pass (if
cadence.auto_critique_before_postis true) - Ships a draft the scorer blocks (
scripts/score_post.pyexit 1 with blockers)
Where things live
- Operator files:
brand-config.json,SOUL.md,drafts/in the operator's project folder. This pack keepsdrafts/rather than the suite'sgtm/folder, for back-compat. - Templates:
SOUL.mdandbrand-config.example.jsonin this repo. The example values are JMC Go-to-Market Systems's, not the operator's. - Scorer:
python3 scripts/score_post.py --file <draft> --soul SOUL.md - State:
python3 scripts/check_setup.py --dir .
Onboarding flow
Missing brand-config + SOUL (or SOUL.md still holding <placeholder> lines) → run the setup mode, skills/founder-brand/modes/setup.md. Shared operator questions and the shared SOUL.md voice sections are asked once for the suite by /gtm:setup.
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.

