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/arcassystems/founderos/bottleneck-diagnosticnpx skills add ARCASSystems/FounderOS --skill bottleneck-diagnosticgit clone --depth 1 https://github.com/ARCASSystems/FounderOSWrote 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/arcassystems/founderos/bottleneck-diagnostic)<a href="https://agentmods.dev/skills/arcassystems/founderos/bottleneck-diagnostic"><img src="https://agentmods.dev/badge/skills/arcassystems/founderos/bottleneck-diagnostic.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.00063 | $0.01040 |
| Opus 5 | $0.00032 | $0.00520 |
| Sonnet 5 | $0.00013 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
bottleneck-diagnostic 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bottleneck Diagnostic
Runs on: reasoning - reads your files and reasons; any capable agent can run this.
This diagnostic finds where the business depends too much on the founder. It can run as a self-assessment or as an external assessment from public signals.
Modes
Mode 1 - Self-Assessment
Use when the founder answers directly.
Mode 2 - External Assessment
Use when the founder is assessing a prospect, partner, or company from public evidence.
Dimensions
Each dimension scores 0 to 20. Higher means more dependency.
1. Decision Dependency
Question: Can decisions happen without the founder in the room?
Self-assessment prompts:
- How many decisions per week require your approval?
- If you were unreachable for 48 hours, what would stop?
- Does the team decide and inform you, or ask first?
- When did someone make a call you disagreed with and you let it stand?
Public signals:
- Founder appears to approve every visible action.
- No leadership team is visible.
- Hiring posts route operational roles to the founder.
2. Client Dependency
Question: Do clients buy the company or the founder?
Self-assessment prompts:
- What percentage of clients would leave if you stopped servicing them?
- Can someone else close a new deal without you?
- Do clients call your personal phone for business issues?
Public signals:
- Testimonials name the founder, not the company.
- Founder is the face of every case study and pitch.
- No account ownership is visible.
3. Process Dependency
Question: Are operations in a system or in the founder's head?
Self-assessment prompts:
- If you hired your replacement tomorrow, how long would handover take?
- How many core processes are documented?
- When something breaks, does the team follow a process or call you?
Public signals:
- Repeated hiring for the same role.
- Vague job posts.
- Founder content mentions being buried in operations.
4. Revenue Dependency
Question: Can revenue continue without daily founder input?
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 · 159 lines · 63 tokens per session scan A 0f362670fcce
bottleneck-diagnostic is a skill published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 22d ago), licensed MIT. It adds 63 tokens to every session and 1,040 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
wiki-ingest
Compile a raw source (document, URL content, meeting notes, research output) into a wikikit agent wiki — merge-don't-overwrite, log contradictions, maintain cross-references, then lint. Use whenever the user says "add this to the wiki", "ingest this", or drops new source material for a wiki maintained with…
markstream-react
Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, next, or server entrypoint, import CSS correctly, choose between content and nodes, keep client boundaries safe, add renderer-local streamingComponents or htmlComponents, use…
markstream-vue2-cli
Integrate markstream-vue2 into a Vue 2 Vue CLI or Webpack 4 app. Use when Codex needs Webpack 4-friendly setup, CDN worker fallbacks for Mermaid or KaTeX, dist/index.css imports, Vue 2 composition-api shims, or code block choices limited to stream-diffs or plain .
publish-report
Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it without being asked…
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.
alive-search
Search across all walnuts -- decisions, people, files, references, insights, log history.