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/meeting-notes)<a href="https://agentmods.dev/commands/killvxk/pm-skills-zh/meeting-notes"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/meeting-notes.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.00023 | $0.00825 |
| Opus 5 | $0.00012 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
meeting-notes 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
/meeting-notes -- 会议纪要整理
将原始会议记录或粗略笔记转化为清晰、结构化的会议纪要，完整记录决策并明确行动项归属。
Invocation（调用示例）
/meeting-notes [粘贴会议记录]
/meeting-notes [上传会议记录文件、音频摘要或笔记]
Workflow（工作流程）
Step 1：接收会议记录
支持以下任意格式输入：
- 完整记录（来自 Otter、Fireflies、Google Meet、Zoom 等工具）
- 会议中记录的粗略笔记
- 转录工具生成的音频摘要或会议回顾
- 多份输入（例如会议记录 + 用户自己的笔记）
若输入内容较少，用现有内容处理，并标注信息缺口。
Step 2：提取与结构化
应用 summarize-meeting 技能：
解析内容，识别以下要素：
- 参与者：出席人员（从自我介绍、发言人标注或提及信息中获取）
- 讨论议题：主要议程项或对话线索
- 已做决策：明确达成的协议或结论
- 行动项：分配的任务，注明负责人和截止日期（如有提及）
- 待解问题：需要后续跟进的未决事项
- 重要引述：值得原文保留的重要表述
- 背景信息：会议类型、项目背景
Step 3：生成会议纪要
## 会议纪要
**日期**: [如已知]
**参与者**: [姓名/角色]
**会议类型**: [站会、规划会、评审会、一对一、干系人会议等]
**主题**: [主要议题]
### 摘要
[3-5 句话概述讨论内容和结论]
### 关键决策
1. **[决策内容]** — [背景和依据]
2. ...
### 行动项
| # | 行动内容 | 负责人 | 截止日期 | 状态 |
|---|--------|-------|---------|------|
### 讨论要点
**[议题 1]**: [核心观点、不同立场、结论]
**[议题 2]**: [核心观点、不同立场、结论]
### 待解问题
- [问题] — 需要 [相关人员/团队] 提供意见
### 后续步骤
- [下一步行动]
- 下次会议：[如有提及]
保存为 Markdown 格式。
Step 4：提供后续建议
- "需要我将这份纪要发送给参与者吗？"
- "需要我根据行动项创建工单吗？"
- "需要我根据所做决策起草一份干系人更新通知吗？"
Notes（注意事项）
- 决策是最有价值的输出——确保每个决策都被清晰记录
- 没有负责人的行动项毫无意义——如未提及负责人，请标注出来
- 摘要要简明扼要——未参会的人应能在 30 秒内了解大意
- 如果会议记录很长（60 分钟以上的会议），在完整摘要前提供一份简短总结（TL;DR）
- 区分"讨论了"和"决定了"——很多议题经过讨论但未达成结论
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 · 90 lines · 23 tokens per session scan A 45e060dae12c
meeting-notes is a command published in the GitHub repository killvxk/pm-skills-zh (154 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 825 once invoked, about $0.0001 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
brand-generate
Generate an on-brand document from a saved Brand Profile.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
convert
Convert a file to Markdown using markitdown.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
render-figures
Compile all .tex and .typ figure files in a directory.