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/williancesar/saasoned/growth-experimentsnpx skills add williancesar/saasoned --skill growth-experimentsgit 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-experiments)<a href="https://agentmods.dev/skills/williancesar/saasoned/growth-experiments"><img src="https://agentmods.dev/badge/skills/williancesar/saasoned/growth-experiments.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 | $0.00096 | $0.01399 |
| Opus 5 | $0.00048 | $0.00700 |
| Sonnet 5 | $0.00019 | $0.00280 |
| Haiku 4.5 | $0.00010 | $0.00140 |
Grade A, and why
growth-experiments 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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth: Experiments
The application engine. Hub: growth-foundations (worldview, shared vocabulary,
router). Every other sibling routes here to convert its framework into a test.
This skill does not own any framework's content — it owns turning content into
a falsifiable, cheap, prioritized experiment and judging the result.
Stance. Nothing scales without a pre-defined traction signal and a kill condition. Vanity metrics are not evidence. Claude refuses to call a result a signal, or to recommend scaling, when the bar wasn't set in advance (hub Guardrails). State the refusal and the reason.
Frameworks index
| Topic | Source | Depth |
|---|---|---|
| Experiment design · cheap test · prioritization · kill condition | Weinberg & Mares, Traction (test cheaply + Bullseye) | references/experiment-design.md |
| North Star / one-metric-that-matters · vanity vs. actionable · CLV > CAC · traction signal | Zero to One (CLV>CAC); growth canon | references/metrics.md |
| Scale-readiness gate · premature scaling · double-down vs. switch | Traction; The Cold Start Problem | references/scale-readiness.md |
The experiment card (default output)
Convert any proposal into this before any spend. Refuse to proceed if a field is blank:
Hypothesis : <specific, falsifiable — "X will cause Y for segment Z">
Framework basis : <which sibling/framework this operationalizes>
Cheapest test : <smallest action that could disprove it, ≤ ~2 weeks>
Primary metric : <one value-backed metric; NOT a vanity metric>
Success / signal: <threshold decided NOW, before running>
Kill condition : <result that ends it — decided NOW>
Timebox : <date/iteration limit>
Decision rule : signal → <next>; kill → <stop/route>; ambiguous → <iterate once, then decide>
A test with no kill condition is a bet — name it as such and refuse to call its outcome a "signal."
Converting each sibling into a test
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.
- 4d ago First seen · 108 lines · 96 tokens per session scan A 37115e902eb1
growth-experiments is a skill published in the GitHub repository williancesar/saasoned (10 stars, last pushed 3mo ago), licensed MIT. It adds 96 tokens to every session and 1,399 once invoked, about $0.0005 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…