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 martineserios/thebrana --skill cold-start-problemgit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/cold-start-problem)<a href="https://agentmods.dev/skills/martineserios/thebrana/cold-start-problem"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/cold-start-problem.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.00168 | $0.03948 |
| Opus 5 | $0.00084 | $0.01974 |
| Sonnet 5 | $0.00034 | $0.00790 |
| Haiku 4.5 | $0.00017 | $0.00395 |
Grade A, and why
cold-start-problem 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 7d 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.
This is a copy
100% identical to cold-start-problem — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Cold Start Problem
A framework for starting and scaling products that live or die by network effects — marketplaces, social apps, messaging, and collaboration tools — distilled from Andrew Chen's The Cold Start Problem. Use it to launch products that are worthless until other users show up, to sequence growth network by network, and to navigate the five stages: the cold start, the tipping point, escape velocity, hitting the ceiling, and the moat.
Core Principle
Network effects start as a liability, not an asset. Value lives in connections between users, and on day one there are none — the same force that makes a dense network unstoppable makes an empty one useless. You don't escape by launching to a market; you escape by building one tiny, complete, self-sustaining network at a time, solving its hard side first, then tipping adjacent networks with a repeatable playbook until the market follows.
Scoring
Goal: 10/10. Rate launch plans and growth strategies for networked products 0-10 against the principles below. Report the current score and the specific changes needed to reach 10/10.
- 9-10: Named atomic network with an instrumented magic moment, hard side solved first, repeatable tipping playbook, density/liquidity metrics, explicit ceiling and moat plan
- 7-8: Clear atomic network and hard-side focus, but tipping tactics are ad hoc or metrics still track totals over density
- 5-6: Network effects acknowledged, but the launch targets a broad market and both sides are treated equally
- 3-4: Generic user-acquisition plan; network thinking limited to "add invites and hope it spreads"
- 0-2: Big-bang launch to everyone at once, vanity signups, no hard-side strategy, no liquidity measures
Framework
1. Network Effects Fundamentals
Core concept: A networked product connects people with each other — buyers with sellers, creators with audiences, coworkers with coworkers — and becomes more valuable as the right people join. Network effects come in three distinct forms: the acquisition effect (the network pulls in its own new users), the engagement effect (more users make each session more valuable), and the economic effect (density improves monetization and unit economics). A product can be strong in one and weak in the others.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 189 lines · 168 tokens per session scan A 6ee3a73a0ab3
cold-start-problem is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed 2d ago), licensed MIT. It adds 168 tokens to every session and 3,948 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cold-start-problem, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
bump-catalog
Promote frequently used mojiemoji variants from the local usage cache into prestamp-catalog.yml and open a deterministic catalog update pull request.
mojiemoji-config
Manage persistent mojiemoji prestamp settings such as intensity in /.config/mojiemoji/config.json.
mojiemoji-github
GitHub issue / PR / review / release bodies for Codex should run through the shared mojiemoji core before posting Japanese Markdown.
eu-ai-act-check
EU AI Act compliance — migrated to pitimon/claude-governance v3.1.0. This stub redirects to the canonical implementation. Maps to H1 (Be Proactive — prevent regulatory crisis) + H8 (Voice/Conscience).
workflow
Guided walkthrough of the 7-step workflow. Prompts at each step to invoke or skip. Use when starting a new feature or when unsure which step comes next.
log
A phase-log command that records completed work in Markdown files, a human-readable text format, and updates an index of phases.