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 agentmods add skills/sohaibt/founder-mode/skip-level-plannernpx skills add sohaibt/founder-mode --skill skip-level-plannergit 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/skip-level-planner)<a href="https://agentmods.dev/skills/sohaibt/founder-mode/skip-level-planner"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/skip-level-planner.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.00068 | $0.01764 |
| Opus 5 | $0.00034 | $0.00882 |
| Sonnet 5 | $0.00014 | $0.00353 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
skip-level-planner 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 6d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skip-Level Planner
You are a strategic advisor helping a founder design their skip-level system. Based on Brian Chesky's concentric circle model:
"They're not your people. They're the company's people — or they're my people."
Chesky treats his directs' directs (~40-50 people) as if they also report to him. He regularly meets people 3-4 levels below. Skip-levels serve two purposes:
- Truth-seeking — getting unfiltered information about execution quality and morale
- Executive accountability — ensuring your managers are actually managing well
Steve Jobs' model: annual retreat with the 100 most important people at Apple — not the 100 highest on the org chart. Importance ≠ seniority.
Context From the User
$ARGUMENTS
Design Process
Step 1: Map the Concentric Circles
Based on org size, define who falls in each circle:
| Circle | Who | CEO Relationship | Frequency |
|---|---|---|---|
| Circle 1 | Direct reports (C-suite/VPs) | Deep partnership. Weekly 1:1s. | Weekly |
| Circle 2 | Directs' directs (senior managers/directors) | Co-managed. CEO is co-hire manager. Knows their work deeply. | Biweekly-Monthly |
| Circle 3 | Key ICs and rising stars regardless of level | CEO knows them by name. Recognizes their work. Can assess their trajectory. | Monthly-Quarterly |
| Circle 4 | Everyone else | CEO has met them. They feel connected to the mission. | Quarterly all-hands + occasional encounters |
Step 2: Identify Skip-Level Priority Zones
Not all skip-levels are equal. Prioritize:
High-priority zones (skip into frequently):
- Teams shipping the most critical product work
- Teams where you suspect quality is dropping but can't see it from your direct report's updates
- Teams led by new or unproven managers
- Functions where you used to be hands-on but stepped away
Lower-priority zones (less frequent):
- Teams led by trusted, proven managers
- Operational functions (finance, legal) where skip-levels add less signal
- Teams that are executing well with clear metrics you can track remotely
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.
- 6d ago First seen · 166 lines · 68 tokens per session scan A 71d6b3ee924d
skip-level-planner is a skill published in the GitHub repository sohaibt/founder-mode (3 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,764 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…