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 sprint-plangit 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/sprint-plan)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/sprint-plan"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/sprint-plan/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/sprint-plan"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/sprint-plan.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.00060 | $0.00652 |
| Opus 5 | $0.00030 | $0.00326 |
| Sonnet 5 | $0.00012 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
sprint-plan 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 10d 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
Sprint 规划
通过估算团队容量、选取和排序故事、识别风险来规划 Sprint（冲刺）。
Context（背景）
你正在帮助规划 $ARGUMENTS 的 Sprint。
如果用户提供了文件（待办清单、速率数据、团队名单或历次 Sprint 报告），请先阅读。
Instructions（操作指南）
-
估算团队容量：
- 团队成员数量及各自可用时间（休假、会议、值班）
- 历史速率（过去 3 个 Sprint 的平均故事点数）
- 容量缓冲：预留 15-20% 用于计划外工作、缺陷修复和技术债务
- 计算以故事点或理想工时表示的可用容量
-
评审并选取故事：
- 从排好优先级的待办清单中取用（优先级最高的优先）
- 验证每个故事是否满足就绪定义（验收标准清晰、已估算、无阻碍）
- 标注在提交前需要细化的故事
- 达到容量上限时停止加入故事
-
映射依赖关系：
- 识别依赖其他故事或外部团队的故事
- 对有依赖关系的故事进行合理排序
- 标注外部依赖及负责人
- 识别关键路径
-
识别风险并制定缓解措施：
- 高不确定性或高复杂度的故事
- 可能延期的外部依赖
- 知识集中（只有一个人能完成）
- 针对每个风险提出缓解建议
-
创建 Sprint 计划摘要：
Sprint 目标：[一句话描述成功的样子] 时长：[2 周 / 1 周 / 等] 团队容量：[X 故事点] 已承诺故事：[跨 Z 个故事，共 Y 故事点] 缓冲：[剩余容量] 故事列表： 1. [故事标题] — [故事点] — [负责人] — [依赖项] ... 风险： - [风险] → [缓解措施] -
定义 Sprint 目标：一句清晰的话，描述本次 Sprint 交付的核心价值。
逐步思考。保存为 Markdown 格式。
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.
- 10d ago First seen · 68 lines · 60 tokens per session scan A e13abff6eafb
sprint-plan is a skill published in the GitHub repository killvxk/pm-skills-zh (158 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 652 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.