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.
git clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote 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/commands/killvxk/pm-skills-zh/north-star)<a href="https://agentmods.dev/commands/killvxk/pm-skills-zh/north-star"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/north-star/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/commands/killvxk/pm-skills-zh/north-star"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/north-star.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.00028 | $0.01181 |
| Opus 5 | $0.00014 | $0.00590 |
| Sonnet 5 | $0.00006 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
north-star 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.
What it actually says
/north-star -- 北极星指标定义
找到最能体现产品价值交付的那个单一指标，以及驱动它的输入指标。识别你的商业模式类型，并对照已验证的标准进行校验。
调用示例
/north-star 面向团队协作的 B2B SaaS 产品
/north-star 通过订阅付费的消费端健身应用
/north-star 帮我重新审视我们的北极星指标——我们在追踪 DAU，但感觉不太对
工作流
第一步：了解产品背景
提问：
- 产品是什么？它为用户创造了什么价值？
- 商业模式是什么？（订阅、交易抽成、广告、平台撮合）
- 目前在追踪哪些指标（如有）？
- 为什么现在需要做这件事？（新产品、现有指标感觉不对、团队对齐需要）
第二步：识别商业模式类型
应用 north-star-metric 技能：
判断产品属于哪种模式：
- 注意力型（Attention）：通过用户时间/参与度变现（媒体、社交、广告支持型产品）
- 交易型（Transaction）：通过购买行为变现（电商、平台撮合）
- 生产力型（Productivity）：通过效率提升变现（SaaS、工具、B2B 产品）
商业模式类型决定了北极星指标的方向。
第三步：定义北极星指标
- 提出 2-3 个候选北极星指标
- 对每个候选指标逐一验证以下 7 条标准：
- 体现了向用户交付的价值
- 是收入的领先指标
- 可度量、可追踪
- 全团队都能理解
- 可干预（团队能够影响它）
- 不是虚荣指标
- 无法在不创造真实价值的情况下被人为刷高
- 推荐最优候选指标并说明理由
第四步：定义输入指标
针对所选北极星指标，识别 3-5 个输入指标：
- 每个输入指标应是直接驱动北极星指标的杠杆
- 每个输入指标应归属于某个具体团队
- 所有输入指标合在一起，应符合 MECE 原则，能够全面解释北极星指标的变动
第五步：生成指标框架文档
## 北极星指标框架：[产品名称]
**商业模式类型**：[注意力型 / 交易型 / 生产力型]
### 北极星指标
**指标**：[精确名称]
**定义**：[计算公式或度量方法]
**选择理由**：[体现用户价值、领先于收入、可干预]
**当前值**：[如已知]
**目标值**：[目标]
### 验证结果
| 标准 | 是否通过 | 说明 |
|------|---------|------|
| 体现用户价值 | [是/否] | [说明] |
| 收入领先指标 | [是/否] | [说明] |
| 可度量 | [是/否] | [说明] |
| 易于理解 | [是/否] | [说明] |
| 可干预 | [是/否] | [说明] |
| 非虚荣指标 | [是/否] | [说明] |
| 不可刷量 | [是/否] | [说明] |
### 输入指标
| 输入指标 | 对北极星指标的驱动方式 | 归属团队 | 当前值 | 目标值 |
|---------|-------------------|---------|------|------|
### 指标星座图
[树形图：北极星指标 → 输入指标 → 团队行动]
### 对冲指标
| 指标 | 防范风险 |
|------|---------|
### 规避的反模式
[说明为何没有选择 DAU、收入或其他常见但有缺陷的指标]
输出内容保存为 Markdown 文件。
第六步：提供后续行动建议
- "需要我围绕这些指标搭建完整的数据看板吗？"
- "需要我基于这些指标制定 OKR吗？"
- "需要我编写 SQL 查询语句来计算这些指标吗？"
注意事项
- 北极星指标应衡量交付的用户价值，而非单纯的活跃行为——"日活用户数"只有在活跃使用等同于价值交付时才是合适的指标
- 收入永远不是好的北极星指标——它是滞后指标，无法反映用户价值
- 输入指标是让整个框架真正可落地的关键——没有输入指标，北极星指标不过是个好看的仪表盘数字
- 每年或在商业模式发生重大变化时，应重新审视北极星指标
- 对冲指标是防范古德哈特定律（Goodhart's Law）的手段——当一个指标成为目标，它就不再是好的度量指标
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 · 114 lines · 28 tokens per session scan A 23bea1cb9918
north-star is a command published in the GitHub repository killvxk/pm-skills-zh (156 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,181 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.