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 serejaris/kimi-skills --skill iteration-plannergit clone --depth 1 https://github.com/serejaris/kimi-skillsWrote 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/serejaris/kimi-skills/iteration-planner)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/iteration-planner"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/iteration-planner/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/serejaris/kimi-skills/iteration-planner"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/iteration-planner.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.00109 | $0.03238 |
| Opus 5 | $0.00055 | $0.01619 |
| Sonnet 5 | $0.00022 | $0.00648 |
| Haiku 4.5 | $0.00011 | $0.00324 |
Grade A, and why
iteration-planner 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.
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planner — 敏捷 Sprint 规划
基于团队产能 (Capacity) 和历史 Velocity，帮助 Scrum Master / PM 完成 Sprint 规划：拆分并分配 Story/Task，检查负载均衡，识别依赖关系，输出可执行的 Sprint 计划。
SOP 流程总览
Step 1: 收集输入 → Step 2: 计算团队产能 → Step 3: 确定 Sprint 目标与范围
→ Step 4: 任务拆分与估点 → Step 5: 依赖分析 → Step 6: 任务分配与负载均衡
→ Step 7: 输出 Sprint 计划 → Step 8: 风险检查与承诺确认
Step 1：收集输入信息
向用户收集以下信息（缺失项需主动询问）：
| 输入项 | 说明 | 示例 |
|---|---|---|
| Sprint 时长 | 迭代周期天数 | 2 周 (10 工作日) |
| 团队成员列表 | 姓名 + 角色 | 张三(前端)、李四(后端)、王五(测试) |
| 各成员可用天数 | 考虑请假、会议、其他项目占用 | 张三 8 天、李四 10 天、王五 9 天 |
| 历史 Velocity | 近 3-5 个 Sprint 的完成故事点 | [32, 28, 35, 30, 33] |
| Product Backlog | 待规划的 Story 列表（含优先级和估点） | 见 Backlog 表 |
| 已知依赖 | Story 之间的前后置关系 | Story-3 依赖 Story-1 完成 |
信息不足时的默认值
- Sprint 时长未指定 → 默认 2 周 (10 工作日)
- 可用天数未指定 → 默认 Sprint 时长 × 0.8（扣除会议和杂务）
- 历史 Velocity 未知 → 使用本次估点总和的 70% 作为保守目标
- 角色未指定 → 按通用开发者处理
Step 2：计算团队产能 (Capacity)
2.1 个人产能计算
个人产能 = 可用天数 × 每日有效工时 × 专注系数
| 参数 | 默认值 | 说明 |
|---|---|---|
| 每日有效工时 | 6 小时 | 8 小时工作日扣除会议、休息等 |
| 专注系数 | 0.8 | 扣除上下文切换、沟通等开销 |
2.2 团队总产能
团队总产能 (人时) = Σ(各成员个人产能)
团队总产能 (故事点) = 参考 Velocity 取值
2.3 产能计算示例
| 成员 | 可用天数 | 有效工时/天 | 专注系数 | 个人产能(人时) |
|---|---|---|---|---|
| 张三 | 8 | 6 | 0.8 | 38.4 |
| 李四 | 10 | 6 | 0.8 | 48.0 |
| 王五 | 9 | 6 | 0.8 | 43.2 |
| 合计 | 129.6 |
Step 3：确定 Sprint 目标与范围
3.1 Velocity 参考值计算
参考 Velocity = 近 N 个 Sprint Velocity 的平均值
建议取 N = 3~5，剔除明显异常值
| 计算方式 | 适用场景 | 说明 |
|---|---|---|
| 简单平均 | 团队稳定 | mean(近 3-5 个 Sprint) |
| 加权平均 | 团队近期有变化 | 近期权重更高 |
| 取最小值 | 保守承诺 | min(近 3 个 Sprint) |
3.2 范围选定规则
- 按优先级从高到低排列 Backlog
- 累加故事点，直到接近但不超过参考 Velocity
- 如最后一个 Story 加入后超出 Velocity 的 110%，则不纳入
- 留出 10-15% 的缓冲用于应急和技术债务
Step 4：任务拆分与估点
4.1 Story 拆分检查
每个 Story 应满足 INVEST 原则：
| 原则 | 含义 | 检查点 |
|---|---|---|
| Independent | 独立 | 是否可单独交付？ |
| Negotiable | 可协商 | 实现方式是否灵活？ |
| Valuable | 有价值 | 是否对用户有明确价值？ |
| Estimable | 可估算 | 团队是否能给出估点？ |
| Small | 小 | 是否能在一个 Sprint 内完成？ |
| Testable | 可测试 | 验收标准是否明确？ |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 295 lines · 109 tokens per session scan A 0488574cc96f
iteration-planner is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 3,238 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".