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 engineer-to-foundergit 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/engineer-to-founder)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/engineer-to-founder"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/engineer-to-founder/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/engineer-to-founder"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/engineer-to-founder.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.00059 | $0.04215 |
| Opus 5 | $0.00030 | $0.02107 |
| Sonnet 5 | $0.00012 | $0.00843 |
| Haiku 4.5 | $0.00006 | $0.00421 |
Grade A, and why
engineer-to-founder 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineer to Founder
Overview
The best companies are built by engineers who became founders — Stripe, GitHub, Zapier, Notion, Figma, Vercel. But being a great engineer doesn't automatically make you a great founder. The transition from IC to CEO requires learning to sell, hire, fire, fundraise, and stare at existential risk without flinching. The mistake: thinking "I'll just build a great product and everything else will figure itself out." This skill covers the complete engineer-to-founder transition: when to quit your job, how to build and sell simultaneously, hiring when you've only ever coded alone, and the mental models that separate engineers who become successful founders from those who stay engineers with side projects.
When to Use
Trigger phrases: "engineer becoming founder", "technical founder", "IC to CEO", "developer starting a startup", "should I quit my job to start a company", "learning to sell as an engineer", "solo developer startup", "how to hire as a technical founder", "indie hacker to startup", "side project to company"
Authoritative Foundations
Patrick Collison (Stripe) — Speed as Strategy
"Move fast. If you're not embarrassed by your first version, you launched too late." Stripe's early advantage wasn't technology — it was speed of execution. They shipped faster than incumbents could respond.
Paul Graham — Maker's Schedule vs. Manager's Schedule
Engineers work in half-day blocks. Meetings destroy deep work. As you become a founder, you'll be pulled toward manager's schedule. Protect maker time ruthlessly. The best technical founders still code.
DHH (37signals/Basecamp) — Profitable From Day 1
"You don't need VC. You don't need to be a unicorn. Build something people pay for. Charge from day 1. Profitability is the ultimate moat."
Pieter Levels — Build in Public
"12 startups in 12 months. Most failed. A few made millions. The ones that worked? I built them in public, got feedback from day 0, and iterated fast."
What ships with it
4 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 · 358 lines · 59 tokens per session scan A d81d3d0fab10
engineer-to-founder is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 4,215 once invoked, about $0.0003 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…