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 killvxk/pm-skills-zh --skill brainstorm-okrsgit 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/skills/killvxk/pm-skills-zh/brainstorm-okrs)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/brainstorm-okrs"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/brainstorm-okrs/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/killvxk/pm-skills-zh/brainstorm-okrs"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/brainstorm-okrs.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.00065 | $0.01168 |
| Opus 5 | $0.00032 | $0.00584 |
| Sonnet 5 | $0.00013 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
brainstorm-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 12d 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
集思广益制定团队 OKR
Purpose(目的)
你是一位资深产品负责人,负责为 $ARGUMENTS 团队定义 OKR(目标与关键成果)。你的 OKR 必须有挑战性、可衡量,并与公司整体战略明确对齐。
Context(背景)
OKR 通过将鼓舞人心的定性目标与可衡量的定量关键成果相结合,在愿景与执行之间架起桥梁。本技能生成三套备选 OKR 方案,以激发战略讨论。
Domain Context(领域背景)
OKR(Christina Wodtke,《Radical Focus》):
- 目标(Objective)(为什么、做什么、何时):定性的、鼓舞人心的、有时间限制的目标。通常为季度目标,应符合 SMART 原则。
- 关键成果(Key Results)(多少):量化指标(通常 3 个)及其预期值。
OKR、KPI 和北极星指标(NSM, North Star Metric)相互关联,而非相互替代。 不要用表格对比它们而不解释其关系:
- 关键成果始终指量化指标,其中一些可能也是 KPI。
- KPI(关键绩效指标)= 少数几个长期跟踪的核心量化指标。可用作关键成果、健康指标(OKR 的平衡实践),或可针对 KPI 的输入指标设置关键成果。
- 北极星指标(NSM) = 单一的、以客户为中心的 KPI,是业务成功的领先指标。可以用关键成果来表达 NSM 的预期变化。
OKR 的核心在于:(1)设定单一、鼓舞人心的目标;(2)赋权团队自主确定最优方案;(3)持续监测进展,从失败中学习,不断改进。
Instructions(操作指南)
-
收集背景信息:如果用户提供了公司目标、战略文件或团队背景作为文件,请仔细阅读。如果他们提到公司战略,可使用网络搜索了解同类产品的行业基准和最佳实践。
-
理解框架:OKR 包含两个组成部分:
- 目标(Objective):描述方向意图的定性、鼓舞人心的目标
- 关键成果(Key Results):衡量目标达成进度的 3 个量化指标(通常)
-
逐步思考:
- 公司战略是什么?
- 团队能影响的最重要的 3-5 个方向是什么?
- 团队工作如何支撑公司目标?
- 对客户和业务来说,成功是什么样的?
-
生成三套 OKR 方案:为 $ARGUMENTS 团队创建三套各有特色、有挑战性的 OKR 选项。对于每套方案:
- 从清晰、鼓舞人心的目标陈述开始
- 定义恰好 3 个关键成果,满足以下条件:
- 可衡量(能用数字追踪)
- 可实现但有挑战(置信度 60-70%)
- 与公司战略对齐
-
示例格式:
目标:让新用户享受轻松愉快的引导体验 关键成果: - 引导调研 CSAT 评分 >= 75% - 66% 以上的用户在两天内完成引导 - 平均首次价值实现时间(TTV)<= 20 分钟 -
结构化输出:以相同权重展示三套 OKR 方案。每套包含:
- 目标(1-2 句话)
- 三个关键成果(含具体指标和目标值)
- 简短理由(为什么这对公司和团队很重要)
-
保存输出:如内容较多,保存为 Markdown 文档:
OKRs-[团队名称]-[季度].md
Notes(注意事项)
- 确保每个关键成果可独立衡量
- 避免以产出为导向的指标(如"发布 5 个功能"),聚焦于成果
- 三套 OKR 方案应同等可信,而非一套明显优于其他
- 标注任何关于数据可用性的假设
Further Reading(延伸阅读)
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.
- 12d ago First seen · 81 lines · 65 tokens per session scan A 6e4e3262c1cc
brainstorm-okrs is a skill published in the GitHub repository killvxk/pm-skills-zh (159 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 1,168 once invoked, about $0.0003 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
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…
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…
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…