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/plan-okrs)<a href="https://agentmods.dev/commands/killvxk/pm-skills-zh/plan-okrs"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/plan-okrs.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.00030 | $0.01124 |
| Opus 5 | $0.00015 | $0.00562 |
| Sonnet 5 | $0.00006 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
plan-okrs 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 8d 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
/plan-okrs -- 团队 OKR 规划
生成结构清晰、能将团队工作与公司战略挂钩的 OKR（目标与关键成果）。输出 3 套 OKR 方案，每套包含定性目标和定量关键成果。
Invocation（调用示例）
/plan-okrs 增长团队 Q2 OKR——公司目标是 ARR（年度经常性收入）增长 50%
/plan-okrs 对齐"提升激活率"目标的用户引导团队 OKR
/plan-okrs [上传公司 OKR 文档或战略文件]
Workflow（工作流程）
Step 1：收集背景信息
向用户询问：
- 这是哪个团队或产品方向的 OKR？
- 覆盖哪个时间段？（季度为标准，也可以是年度或自定义周期）
- 需要对齐哪些公司级目标？
- 上个季度的情况如何？（成果、未达成项、经验教训）
- 是否有已知约束条件或优先事项？
可接受上传公司 OKR 文档或战略文件。
Step 2：生成 OKR
应用 brainstorm-okrs 技能：
- 创建 3 套 OKR 方案（每套包含 1 个目标 + 3-5 个关键成果）
- 目标（Objective）：定性的、鼓舞人心的、有挑战但可实现的、行动导向的
- 关键成果（Key Results）：可量化、可衡量、有时间限制、归属明确
- 确保 OKR 与公司目标的对齐关系清晰可见
- 平衡领先指标（活动指标）与滞后指标（成果指标）
Step 3：验证 OKR 质量
对照最佳实践检验每条 OKR：
- 目标是否鼓舞人心？（能否凝聚团队？）
- 关键成果是否可衡量？（能否用数据而非主观判断来验证完成情况？）
- 目标是否有挑战但不至于让团队沮丧？（达成 70% = 校准良好）
- 每个目标的关键成果是否为 3-5 个？（更多意味着失焦）
- 关键成果是否存在刷数字的空间？（例如"发布 5 个功能"会激励堆功能而非创造价值）
标注问题并提出改进建议。
Step 4：展示并迭代
## 团队 OKR：[团队名称] — [时间段]
**对齐目标**: [公司目标]
### 目标 1：[鼓舞人心的定性描述]
| # | 关键成果 | 基准值 | 目标值 | 负责人 |
|---|---------|--------|--------|--------|
| KR1 | [可量化成果] | [当前值] | [目标值] | [团队/人员] |
| KR2 | ... | ... | ... | ... |
| KR3 | ... | ... | ... | ... |
### 目标 2：[鼓舞人心的定性描述]
[同上格式]
### 目标 3：[鼓舞人心的定性描述]
[同上格式]
### 对齐关系图
公司目标 → 团队目标 → 关键成果 → 预期影响
### 评分指南
- 0.0-0.3：明显未达成——深入分析并总结经验
- 0.4-0.6：有所进展但未达预期
- 0.7-0.9：有挑战的伸展目标校准良好——这是目标区间
- 1.0：完美达成，或目标本身不够有挑战性
### 复盘节奏
- **每周**：对每个关键成果做简短的红黄绿状态更新
- **季中**：深度复盘，如背景有变化则调整目标
- **季末**：打分、反思，输入下季度规划
后续建议：
- "需要我调整挑战力度——让目标更激进或更保守吗？"
- "需要我创建指标看板来跟踪这些 OKR 吗？"
- "需要我起草干系人更新通知来介绍这些 OKR 吗？"
Notes（注意事项）
- OKR 应描述成果，而非产出（"将激活率提升 20%"而非"完成用户引导改版"）
- 如果用户没有公司 OKR，帮助他们从产品战略或业务目标推导出团队目标
- 每个团队每季度最多 3 个目标——更多意味着失焦
- 关键成果应该是伸展目标——如果你确信一定能达成，说明它不够有挑战性
- 标注任何可能被刷数字的关键成果，并建议一个制衡指标
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.
- 8d ago First seen · 99 lines · 30 tokens per session scan A 2366e5f1e534
plan-okrs is a command published in the GitHub repository killvxk/pm-skills-zh (154 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,124 once invoked, about $0.0002 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.