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 retrogit 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/retro)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/retro"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/retro/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/retro"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/retro.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.00069 | $0.00821 |
| Opus 5 | $0.00034 | $0.00411 |
| Sonnet 5 | $0.00014 | $0.00164 |
| Haiku 4.5 | $0.00007 | $0.00082 |
Grade A, and why
retro 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
Sprint 回顾会引导工具
运行结构化的回顾会，浮现洞察并产出可落地的改进措施。
Context（背景）
你正在为 $ARGUMENTS 组织回顾会。
如果用户提供了文件（Sprint 数据、速率图表、团队反馈或历次回顾笔记），请先阅读。
Instructions（操作指南）
-
根据背景选择回顾格式（或让用户选择）：
格式 A — Start / Stop / Continue（开始/停止/继续）：
- 开始：我们应该开始做什么？
- 停止：我们应该停止做什么？
- 继续：哪些做得好，应该继续保持？
格式 B — 4Ls（喜欢/学到/缺少/期望）：
- Liked 喜欢：团队喜欢什么？
- Learned 学到：获得了哪些新知识？
- Lacked 缺少：缺少了什么？
- Longed For 期望：希望拥有什么？
格式 C — 帆船模型：
- 风（推进力）：什么在驱动我们前进？
- 锚（阻力）：什么在拖慢我们？
- 礁石（风险）：前方有哪些危险？
- 岛屿（目标）：我们想要到达哪里？
-
如果用户提供了原始反馈（如便利贴、问卷回复、Slack 消息）：
- 将相似条目归类为主题
- 识别被提及最多的话题
- 注意情绪规律（挫败感、干劲、困惑）
-
分析 Sprint 表现：
- Sprint 目标：是否达成？
- 速率与承诺对比（过度承诺？承诺不足？）
- 遇到的阻碍及解决方式
- 协作模式（哪些有效，哪些无效）
-
生成优先级行动项：
优先级 行动项 负责人 截止日期 成功指标 1 [具体、可落地的改进] [姓名/角色] [日期] [如何判断是否有效] - 限制在 2-3 个行动项（更多会没人执行）
- 每个必须具体、可分配、可衡量
- 如有历次回顾笔记，回顾上次行动项——是否已完成？
-
生成回顾会摘要：
## Sprint [X] 回顾会 — [日期] ### Sprint 表现 - 目标：[达成 / 部分达成 / 未达成] - 承诺：[X 点] | 完成：[Y 点] ### 关键主题 1. [主题] — [摘要] ### 行动项 1. [行动] — [负责人] — [截止日期] ### 上次回顾跟进 - [上次行动] — [状态：已完成 / 进行中 / 未开始]
保存为 Markdown 格式。保持建设性语气——目标是改进，而非追责。
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 · 77 lines · 69 tokens per session scan A e24cc5dac40e
retro is a skill published in the GitHub repository killvxk/pm-skills-zh (156 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 821 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.