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 williancesar/saasoned --skill growth-traction-channelsgit clone --depth 1 https://github.com/williancesar/saasonedWrote 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/williancesar/saasoned/growth-traction-channels)<a href="https://agentmods.dev/skills/williancesar/saasoned/growth-traction-channels"><img src="https://agentmods.dev/badge/skills/williancesar/saasoned/growth-traction-channels/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/williancesar/saasoned/growth-traction-channels"><img src="https://agentmods.dev/badge/skills/williancesar/saasoned/growth-traction-channels.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.00088 | $0.01223 |
| Opus 5 | $0.00044 | $0.00611 |
| Sonnet 5 | $0.00018 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
growth-traction-channels 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth: Traction Channels
Owns channel selection and operations. Hub: growth-foundations (worldview,
shared vocabulary, router). This sibling does not redefine hub terms.
Stance. There are 19 channels; you brainstorm all, test the inner ring cheaply, and focus the ONE that shows a traction signal. Spreading effort across many channels is the default failure, not a hedge.
Frameworks index
| Framework | Source | Depth |
|---|---|---|
| The 19 traction channels | Weinberg & Mares, Traction | references/nineteen-channels.md |
| Bullseye (brainstorm → rank → test → focus) | Traction | references/bullseye.md |
| Distribution power law + the dead zone + CAC | Thiel & Masters, Zero to One | references/distribution-power-law.md |
Bullseye — the operating procedure (checklist)
- Brainstorm. One concrete idea for every one of the 19 channels — no skipping a channel because it "feels wrong." (See the catalog.)
- Rank into rings. Inner = 3 most promising, testable now. Middle = possible. Outer = long shots. Rank on plausible reach × cost × time-to-signal for this product's beachhead.
- Test the inner ring — cheaply, in parallel. Each test answers: roughly what does it cost to acquire a customer here, how many are reachable, are they the right ones? Cheap = days-to-2-weeks, small spend, a kill condition.
- Focus the ONE. If a channel shows a traction signal, drop the others and pour effort into it until it tops out (the distribution power law: one channel usually dominates).
- Re-run Bullseye only when the focused channel saturates or breaks — not
before. (Signal threshold / kill condition:
growth-experiments.)
The 50% rule and Critical Path are hub worldview — apply them, don't restate.
Decision cues
- "Which channel?" with zero users → full Bullseye pass; do not pre-judge.
- "Add another channel?" → only if the current one is saturated and shows a signal. Otherwise this is premature diversification — refuse and cite.
- "Scale this channel" with no signal yet → refuse (hub Guardrail 1). Cite Bullseye/50% rule; design the cheap test instead.
- CAC seems too high and unfixable → check the dead zone (Zero to
One): order value too small for direct sales, too large for viral/ads. Fix
is usually positioning/pricing (route to
growth-positioning), not a new ad set. - "It works for me but doesn't pull new users" → likely a network product,
not a channel problem → route to
growth-network-effects.
What ships with it
3 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.
- 9d ago First seen · 90 lines · 88 tokens per session scan A b5a275425573
growth-traction-channels is a skill published in the GitHub repository williancesar/saasoned (10 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 1,223 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…