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 deciqAI/knowledge-skills --skill bootstrapping-vs-raisinggit clone --depth 1 https://github.com/deciqAI/knowledge-skillsWrote 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/deciqai/knowledge-skills/bootstrapping-vs-raising)<a href="https://agentmods.dev/skills/deciqai/knowledge-skills/bootstrapping-vs-raising"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/bootstrapping-vs-raising/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/deciqai/knowledge-skills/bootstrapping-vs-raising"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/bootstrapping-vs-raising.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.00087 | $0.00693 |
| Opus 5 | $0.00044 | $0.00347 |
| Sonnet 5 | $0.00017 | $0.00139 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
bootstrapping-vs-raising 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 10d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrapping vs Raising — Choose the Fuel to Match the Fire
Overview
Raising venture capital is not a milestone; it's a choice that commits you to a specific outcome — a large, fast, high-multiple exit — because that's the only outcome that pays back the model. Bootstrapping keeps control and optionality but caps speed to what cash flow allows. The right answer depends on the business's true ceiling and the founder's goals, not on what's fashionable.
The Process
- Test venture-scale honestly — is there a plausible path to a very large market and outsized return? Gate: no venture-scale outcome = VC is the wrong fuel; raising forces growth the business can't sustain.
- Clarify the founder's goal — control and durable cash flow, or a big swing at a large exit? These point to different paths.
- Check if the opportunity is speed-sensitive — winner-take-most / land-grab markets reward capital; slow-compounding niches don't.
- Price the cost of capital — dilution + board + the growth-at-all-costs treadmill vs the slowness and personal risk of bootstrapping.
- Consider the middle — revenue-based financing, angels, grants, customer prepayments (non-dilutive fuel).
- Decide and align burn to the path. Gate: bootstrapping while spending like a funded startup is the worst of both — match spend to the chosen fuel.
When to Use
- The "should we raise?" moment
- Weighing an inbound investor against staying independent
- Setting a funding strategy for the next stage
Applying It Well
- Most SMBs and lifestyle-strong businesses are better bootstrapped; VC suits a minority.
- Raising narrows acceptable outcomes — go in eyes open.
- Non-dilutive options are underused; look before diluting.
Red Flags
- Raising because peers did, without a venture-scale case.
- Spending at funded-startup burn while bootstrapped.
- Ignoring revenue-based/grant/prepayment alternatives.
Verification
- Venture-scale outcome honestly assessed
- Founder goal (control vs big exit) made explicit
- Cost of capital vs speed weighed
- Burn matched to the chosen funding path
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.
- 10d ago First seen · 44 lines · 87 tokens per session scan A 49c83461a4f8
bootstrapping-vs-raising is a skill published in the GitHub repository deciqAI/knowledge-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 87 tokens to every session and 693 once invoked, about $0.0004 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
invoice-chase
Runs collections on late invoices: builds an aging ladder (current/30/60/90+), assigns each invoice a rung on an escalation sequence with ready-to-send emails — friendly nudge, firm reminder with late-fee mention, final notice — plus a phone script, tone rules that preserve the relationship, a chase log, and…
review-contract
Clause-by-clause contract review — inventories key clauses (term, termination, liability cap, indemnity, IP, payment, confidentiality, governing law, auto-renewal), flags deviations from market-standard positions with RED/YELLOW/GREEN severity and verbatim quotes, drafts redline language, and sets negotiation…
audit-support
Gets the books audit-ready: builds the PBC (prepared-by-client) list by area, drafts walkthrough narratives for key cycles (revenue, purchases, payroll), matches auditor samples to support, prepares tie-out schedules, tracks open items with owners and due dates, and drafts responses to findings. Use when the user says…
financial-statements
Builds a full statement set — P&L, balance sheet, and indirect cash flow — from a trial balance or transaction export, mapping accounts to a standard chart and proving every tie-out in code. Use when the user says 'build a P&L from this trial balance', 'turn this export into financials', 'I need a balance sheet for…
journal-entry
Drafts correct double-entry journal entries from described business events, with templates for accruals, deferrals, depreciation, payroll, prepaids, and corrections. Every entry carries a date, memo, and support reference; reversals are drafted where due; a running debits-equal-credits check covers each entry and the…
plan-payroll
Plans payroll cash: true loaded cost per hire (gross plus employer taxes, benefits, tools), a payroll calendar with cutoffs and cash-out dates, a scenario table for new hire vs raise vs contractor-vs-employee, and a payroll-to-revenue check against rough industry bands. Use when the user asks "can I afford to hire"…