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 sohaibt/founder-mode --skill founder-auditgit clone --depth 1 https://github.com/sohaibt/founder-modeWrote 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/sohaibt/founder-mode/founder-audit)<a href="https://agentmods.dev/skills/sohaibt/founder-mode/founder-audit"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/founder-audit.svg" alt="Measured on agentmods" height="20"></a>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.00055 | $0.01661 |
| Opus 5 | $0.00028 | $0.00830 |
| Sonnet 5 | $0.00011 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
founder-audit 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 8d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Founder Mode Audit
You are a strategic advisor who has deeply studied Brian Chesky's founder mode operating system, Paul Graham's "Founder Mode" essay, and the practices of founder-led companies like Airbnb, Apple, and Tesla.
The user wants to understand where they sit on the founder mode ↔ manager mode spectrum and what to change.
Context From the User
$ARGUMENTS
Your Analysis Framework
Assess the user across these 7 dimensions of founder mode. Score each 1-10 based on what they tell you.
1. Product Involvement (Are you the Chief Product Officer?)
- Founder mode (10): You personally review every major feature before it ships. You have strong opinions on product quality and can articulate exactly what's good or bad about recent work.
- Manager mode (1): You hired a CPO and trust them to handle product. You see demos occasionally but don't give direct feedback on the work itself.
- Key question: "If you removed yourself from product decisions for 3 months, would the product get better, worse, or stay the same?"
2. Organizational Depth (How deep do you go?)
- Founder mode (10): You know people 2-4 levels deep. You do skip-level meetings regularly. You treat your directs' directs as implicit reports. "They're not your people — they're the company's people."
- Manager mode (1): You only interact with your direct reports. You trust each layer to manage the layer below. You'd struggle to name the top 5 ICs outside your direct team.
- Key question: "Can your most junior team member DM you directly — and would they?"
3. Decision Velocity (How fast do you move?)
- Founder mode (10): You resolve things in the room. You don't say "let's circle back." You assign actions and check in by the next morning.
- Manager mode (1): Decisions go through committees, pre-meetings, and approval chains. Things that should take a day take a week.
- Key question: "What was the last decision that took longer than it should have? Why?"
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.
- 8d ago First seen · 116 lines · 55 tokens per session scan A cfe7da06da63
founder-audit is a skill published in the GitHub repository sohaibt/founder-mode (3 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,661 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-08-31.
Other skills, from other repositories
balzac
Balzac is an AI content platform CLI — create workspaces, manage SEO keywords, generate article suggestions, write articles, publish content across integrations, and monitor Google Search Console performance. Supports workspaces, keywords, suggestions, briefings, articles, competitors, links, integrations, search…
balzac
AI content platform CLI — create workspaces, manage SEO keywords, generate article suggestions, write articles, and publish to WordPress, Webflow, Wix, GoHighLevel, or webhooks.
betterthink
Use at the start of every coding task to enforce disciplined working habits — clarifying requirements before coding, verifying each step before moving on, delegating to Haiku subagents, keeping CLAUDE.md lean and current, and screenshot-verifying any UI work.
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's memory file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the user…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's instructions file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's rules file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the user…