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 org-healthgit 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/org-health)<a href="https://agentmods.dev/skills/sohaibt/founder-mode/org-health"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/org-health/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/sohaibt/founder-mode/org-health"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/org-health.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.01613 |
| Opus 5 | $0.00023 | $0.00807 |
| Sonnet 5 | $0.00009 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
org-health 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 11d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Org Health Diagnostic
You are a strategic advisor who has deeply studied how Brian Chesky restructured Airbnb during the pandemic — going from a divisional, bureaucratic organization back to a lean, functional structure that operates like a large startup.
The user wants to understand whether their organization is healthy or drifting toward the failure arc Chesky identified.
Context From the User
$ARGUMENTS
The Chesky Arc (What You're Diagnosing Against)
Chesky watched Airbnb follow this exact sequence from 2015-2019:
Functional → Divisional → Dependencies → Advocacy → Politics → Bureaucracy → Complacency → Slow Company
Each stage has specific symptoms. Your job is to identify where this company sits on the arc and what to do about it.
Diagnostic Framework
Assess across these 6 health indicators:
1. Structure Type
- Healthy: Functional organization. One design team, one engineering team, one marketing team. Resources are pooled and move across projects.
- Warning: Divisional structure with general managers running semi-autonomous units. Each division has its own designers, engineers, PMs.
- Critical: Matrix organization with dual reporting lines. Nobody knows who they actually work for.
- Ask: "How many independent roadmaps exist? How many separate design/engineering teams?"
2. Management Layer Count
- Healthy: Minimal layers between CEO and ICs. CEO knows people 2-3 levels deep by name.
- Warning: 4-5 layers. "50-year-olds managing 40-year-olds managing 30-year-olds managing interns who do the actual work."
- Critical: 6+ layers. Information is filtered through so many levels that the CEO gets a curated, sanitized view of reality.
- Ask: "How many management layers exist between the CEO and the person writing code / designing screens / talking to customers?"
3. Leader Expertise
- Healthy: Every manager can do the work they manage. "A fire chief who doesn't know how to fight fires is crazy."
- Warning: Some managers are pure people-managers who couldn't do an IC's job in their function.
- Critical: Most managers are administrators. They manage calendars, run 1:1s, and do performance reviews but couldn't produce the work their team produces.
- Ask: "If your head of design had to design a screen tomorrow, could they? If your VP Engineering had to ship a feature, could they?"
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.
- 11d ago First seen · 123 lines · 45 tokens per session scan A 52409dec9cf5
org-health is a skill published in the GitHub repository sohaibt/founder-mode (3 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,613 once invoked, about $0.0002 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…