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/peterfei/forge-skill/growth-hacking-skillnpx skills add peterfei/forge-skill --skill growth-hacking-skillgit clone --depth 1 https://github.com/peterfei/forge-skillWrote 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/peterfei/forge-skill/growth-hacking-skill)<a href="https://agentmods.dev/skills/peterfei/forge-skill/growth-hacking-skill"><img src="https://agentmods.dev/badge/skills/peterfei/forge-skill/growth-hacking-skill.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.00081 | $0.02779 |
| Opus 5 | $0.00041 | $0.01389 |
| Sonnet 5 | $0.00016 | $0.00556 |
| Haiku 4.5 | $0.00008 | $0.00278 |
Grade A, and why
growth-hacking-skill 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 6d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
增长黑客 · 思维工具
"A growth hacker is a person whose true north is growth." — Sean Ellis
激活条件与触发词
- 直接调用：「用增长黑客分析...」「增长诊断...」「做增长实验」
- 语义触发：用户提到留存下降、获客成本高、增长停滞、转化率低
- 组合调用：「先用增长黑客找增长杠杆，再用精益创业验证」
方法框架概览
增长黑客的核心是将增长视为一个可系统化实验的过程，它通过北极星指标锚定方向、全漏斗每层优化、找到啊哈时刻来驱动可持续的增长引擎。
核心原理（3-7个，每个须附 ≥2 个跨域证据）
原理 1: 增长是一个可系统化实验的过程
一句话定义：增长不是靠一次大动作，而是由无数小实验持续驱动。
跨域证据：
- 云存储：Dropbox 通过多轮 A/B 测试发现邀请机制的最优参数（来源：Dropbox Growth Study, 2010）
- 电商：Amazon 持续迭代推荐算法，每个改动有实验数据支撑（来源：Bezos 1997-2010 致股东信合集）
应用方式：建立"假设→实验→测量→决策"循环，每月至少完成 10 个增长实验。
局限：实验需要足够样本量。小产品（DAU<1000）的实验数据噪声大，统计显著性不足。
原理 2: 北极星指标锚定方向
一句话定义：一个单一的、反映用户核心价值的指标，所有增长实验对齐它。
跨域证据：
- 视频流媒体：Netflix 以观看时长替代订阅数作为北极星（来源：Netflix TechBlog, 2015）
- 通讯：WhatsApp 以日均消息发送量而非 DAU 为北极星（来源：WhatsApp Blog, 2014）
应用方式：每个实验问"如果我赢了，北极星会动吗？"不会动的实验优先级降低。
局限：选错北极星会导致有害优化（如以页面浏览量为北极星导致标题党）。
原理 3: 全漏斗每层独立优化
一句话定义：获客、激活、留存、变现、传播不是同一个问题。
跨域证据：
- 社交：Facebook 发现增长瓶颈不在获客而在激活——"10 friends in 7 days"规则（来源：Palihapitiya, Growth at Facebook, 2013）
- 图片社区：Pinterest 瓶颈不是获客而是新用户没有 Pin 可互动（来源：Pinterest Engineering Blog, 2013）
应用方式：用 AARRR 模型逐层诊断，找到断裂点再聚焦优化。不同时对五层做实验。
局限：漏斗层级间有相互影响，孤立优化某层可能导致另一层崩坏。
原理 4: 啊哈时刻是增长引擎的燃料
一句话定义：用户第一次感到"这东西真有用"的那一刻决定了是否留存。
跨域证据：
- 云存储：Dropbox 的 Aha 是第一次文件同步成功（来源：Houston, Dropbox Growth Story, 2011）
- 企业协作：Slack 发现团队发送 2000 条消息后就成了日常必需工具（来源：Butterfield, Slack 内部数据, 2014）
应用方式：找到 Aha Moment 后反向设计新用户引导，让用户尽快到达那一刻。
局限：不是所有产品都有一个明确的 Aha Moment。工具型产品价值是累积的。
原理 5: 数据驱动假设，而非数据驱动决策
一句话定义：用数据生成假设、用实验验证假设，而非让数据替你做决定。
跨域证据：
- 搜索：Google 20% 时间项目不是数据分析出来的，但进展用数据追踪（来源：Google Founders' Letter, 2004）
- 视频平台：YouTube 从星级评分改为点赞/踩是基于行为假设，非数据直接要求（来源：YouTube Creator Blog, 2010）
应用方式：看数据找"哪里不对劲"，提出"为什么"的假设，设计实验验证。
局限：过度依赖历史数据会错过颠覆性机会（如 iPhone 上市前调研不支持触屏手机）。
操作协议（Agentic Protocol）
Step 1: 问题分类
适用信号：
- 产品有 PMF 但增长停滞或放缓
- 用户规模可观但留存/变现有问题
- 需要系统性寻找增长杠杆
不适用信号：
- 产品还没有 PMF（适用精益创业）
- B2B 大客户销售模式（增长黑客擅长自助式增长）
- 品牌和声誉类长期决策
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.
- 6d ago First seen · 194 lines · 81 tokens per session scan A adb03838c33d
growth-hacking-skill is a skill published in the GitHub repository peterfei/forge-skill (13 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 2,779 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-30.
Other skills, from other repositories
descend
Verifies whether the problem was correctly identified before solving, auditing pattern matches against first principles.
fundraising-narrative
This skill should be used when the user asks about "pitch deck", "fundraising story", "investor pitch", "VC narrative", "pitch narrative", "fundraising deck", "pitch structure", "Sequoia format", "why now slide", "market size slide", "TAM SAM SOM", "earned secret", "value hypothesis", "product-market fit"…
investor-relations
This skill should be used when the user asks about "investor update", "board deck", "board meeting", "investor communication", "monthly update", "quarterly update", "investor email", "bad news investors", "pivot communication", "crisis communication investors", "investor ask", "warm intro", "VC relationship"…
ux-principles
User research, usability heuristics, user psychology, accessibility, inclusive design, user testing, and UX metrics.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.