Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add LeadMagic/gtm-skills --skill co-founder-dynamicsgit clone --depth 1 https://github.com/LeadMagic/gtm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/leadmagic/gtm-skills/co-founder-dynamics)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/co-founder-dynamics"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/co-founder-dynamics/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/co-founder-dynamics"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/co-founder-dynamics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00091 | $0.04215 |
| Opus 5 | $0.00046 | $0.02107 |
| Sonnet 5 | $0.00018 | $0.00843 |
| Haiku 4.5 | $0.00009 | $0.00421 |
Grade A, and why
co-founder-dynamics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Co-Founder Dynamics
Overview
The co-founder relationship is the #1 predictor of startup success or failure — ahead of product, market, or funding. YC data shows that co-founder conflict is the leading cause of early-stage startup death. The mistake: choosing a co-founder based on friendship or availability instead of complementary skills, aligned values, and tested working relationships. This skill covers finding co-founders, structuring equity, drafting agreements, building trust, and navigating the hard conversations before they become fatal.
When to Use
Trigger phrases: "find a co-founder", "co-founder equity split", "co-founder agreement", "technical co-founder", "business co-founder", "co-founder dynamics", "should I have a co-founder", "solo vs co-founder", "co-founder breakup", "vesting schedule for founders", "founder prenup"
Authoritative Foundations
Noam Wasserman — The Founder's Dilemmas
The single most important book on founding teams. Key finding: 65% of high-potential startups fail due to co-founder conflict, not product or market issues. The "Rich vs. King" dilemma: every founder must choose between maximizing wealth (taking less equity to attract a great co-founder) or maintaining control (keeping more equity but limiting growth).
YC on Co-Founders
- Sam Altman: "Don't start a startup alone. The data is overwhelming."
- Michael Seibel: "Find someone you've worked with before. Don't find a co-founder — work with people until one becomes your co-founder."
- Dalton Caldwell: "The best co-founder relationships are tested under stress before incorporation. Ship projects together first."
- Paul Graham: "The ideal number of founders is 2 or 3."
First Round Review — Co-Founder DNA
"Before you write a line of code, you need alignment on: ambition level (lifestyle vs. unicorn), risk tolerance, work ethic expectations, and what 'success' means to each founder."
Should You Have a Co-Founder?
Solo Founder — When It Works
- You've raised before and have a network
- Your product is simple enough for one person to build and sell
- You're in a niche market that doesn't require speed-to-market
- You have strong emotional resilience (it's lonely)
- You're fine with 100% of a smaller pie vs. 50% of a bigger one
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 410 lines · 91 tokens per session scan A a856923b610f
co-founder-dynamics is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 4,215 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
onboarding-handoff
Run the Won→onboarding handoff — the seam most teams drop. Trigger when a deal is marked won/closed-won, when the user says "we won X", "hand this off to onboarding", "kick off the new customer", or "onboarding checklist".
product-signal
Route post-sale and field signals into product's roadmap queue, and write the buyer-facing line for anything shipped. Trigger when the user says "what should product hear", "triage the roadmap signals", "route this to product", "feature request", or "what does this feature mean for the buyer".
client-health-review
Sweep every client folder and report what needs attention — renewals inside 90 days, accounts in their first 90 days, missing success definitions, accounts with no QBR in two quarters, unfilled proof stubs, stale reviews, and referral-ready accounts. Use for portfolio review, retention review, or before starting new…
client-onboarding
Turn a won deal into a first-90-days plan with a written success definition, named stakeholders and what each judges success by, and checkpoints at day 14, 30, and 90. Use right after a win, when a new client starts, or when an existing account has no agreed definition of what success means.
session-relay
Maintain lightweight project continuity for long GTM Brain builds by keeping a relay README as the source of truth, archiving transcript links without reading them by default, and producing concise handoff prompts.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…