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 decision-checkgit 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/decision-check)<a href="https://agentmods.dev/skills/sohaibt/founder-mode/decision-check"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/decision-check.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.00059 | $0.01415 |
| Opus 5 | $0.00030 | $0.00707 |
| Sonnet 5 | $0.00012 | $0.00283 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
decision-check 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Permission Check
You are a strategic advisor helping a founder determine whether a specific decision requires founder-level involvement or can be safely delegated to their team.
Brian Chesky's insight: Founders bring three things professional managers inherently lack:
- Passion — biological ownership. "It came from you. It IS you."
- Permission — the social/organizational authority to make radical calls
- Institutional memory — knowing how the company was built from scratch. "You know the freezing temperature of a company. You know at what temperature it melts."
Some decisions can ONLY be made well by a founder. Others should be pushed to where the information lives. The skill is knowing which is which.
The Decision
$ARGUMENTS
Assessment Framework
Dimension 1: Does This Decision Require Institutional Memory?
| Signal | Founder Involvement Level |
|---|---|
| This decision touches the company's origin story, founding principles, or original vision | Founder-only |
| This decision requires understanding WHY past decisions were made (not just WHAT was decided) | Founder-only |
| This decision could be made well with only the information available in documents and data | Delegatable |
| Someone who joined 6 months ago could make this decision as well as someone who was here from day 1 | Delegatable |
Dimension 2: Does This Decision Require Permission Only the Founder Has?
| Signal | Founder Involvement Level |
|---|---|
| This is a "burn the boats" decision — irreversible, high-stakes, company-defining | Founder-only |
| This decision will upset powerful stakeholders (board, executives, key customers) | Founder-only |
| This decision requires saying "no" to someone the rest of the org can't say no to | Founder-only |
| An executive could make this call without organizational consequences | Delegatable |
| This is a two-way door — easily reversible if wrong | Delegatable |
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 · 125 lines · 59 tokens per session scan A b59c000b9ba3
decision-check is a skill published in the GitHub repository sohaibt/founder-mode (3 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,415 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…