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 ramen-profitabilitygit 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/ramen-profitability)<a href="https://agentmods.dev/skills/deciqai/knowledge-skills/ramen-profitability"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/ramen-profitability/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/ramen-profitability"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/ramen-profitability.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.00078 | $0.00691 |
| Opus 5 | $0.00039 | $0.00345 |
| Sonnet 5 | $0.00016 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
ramen-profitability 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 9d 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.
Ramen Profitability & Default Alive/Dead
Overview
Ramen profitability (Paul Graham) = the startup makes just enough to cover the founders' basic living costs. It matters because it flips the company from default dead (will run out of money on the current trajectory) to default alive (reaches profitability before the money runs out) — which changes every decision: you stop being at investors' mercy and buy unlimited time. The core question every founder should be able to answer instantly: default alive or default dead?
The Process
- Compute the honest number — monthly revenue, gross margin, and total burn (include founder living costs).
- Answer default alive/dead — at current growth and spend, do you reach profitability before cash + committed funding runs out? Gate: if you can't answer this in a sentence, stop and build the model now.
- If default dead, act early — the trap is discovering it too late to fix. Two levers: grow revenue faster, or cut burn to reach ramen.
- Target ramen first — covering founders' basics is a huge psychological and strategic unlock; it's often nearer than a full "profitable business."
- Protect the path — don't add fixed costs that push profitability past your runway. Gate: any hire/spend that moves the default-alive date past runway needs an explicit funding plan.
- Re-check monthly — the answer moves with growth and spend.
When to Use
- Uncertain runway / fundraising pressure
- Deciding whether to cut costs or raise
- Bootstrapping toward survival independence
Applying It Well
- Cutting to ramen is usually faster and safer than assuming a raise closes.
- Ramen buys time, which buys options — it's leverage, not smallness.
- Ask the question early; late discovery is what kills.
Red Flags
- Not knowing default alive/dead off the top of your head.
- Assuming a future raise instead of controlling the burn you control.
- Adding fixed cost that pushes profitability past runway.
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.
- 9d ago First seen · 44 lines · 78 tokens per session scan A 6ff01f794d3d
ramen-profitability is a skill published in the GitHub repository deciqAI/knowledge-skills (10 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 691 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-09-03.
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…
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…
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"…
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…
tax-prep
Organizes tax season — an organizer, not tax advice: a document checklist by category (income, expenses, assets, payroll, prior filings), an expense-category sweep that flags plausibly missed deductions in generic jurisdiction-agnostic categories, a quarterly-estimate calendar template, a clean handoff pack for the…