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 malue-ai/dazee-small --skill meeting-notes-to-action-itemsgit clone --depth 1 https://github.com/malue-ai/dazee-smallWrote 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/malue-ai/dazee-small/meeting-notes-to-action-items)<a href="https://agentmods.dev/skills/malue-ai/dazee-small/meeting-notes-to-action-items"><img src="https://agentmods.dev/badge/skills/malue-ai/dazee-small/meeting-notes-to-action-items/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/malue-ai/dazee-small/meeting-notes-to-action-items"><img src="https://agentmods.dev/badge/skills/malue-ai/dazee-small/meeting-notes-to-action-items.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.00025 | $0.00608 |
| Opus 5 | $0.00013 | $0.00304 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
meeting-notes-to-action-items 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
会议纪要转行动项
将会议纪要或讨论记录快速转化为结构化的行动项清单。
使用场景
- 用户说「把这个会议纪要整理成待办」「提取一下行动项」
- 用户贴入一段会议记录，需要快速整理出谁做什么
- 会议结束后需要发送行动项跟踪邮件
执行方式
直接使用 LLM 能力分析文本，无需额外工具。
提取规则
- 识别行动项：从讨论中找出需要有人去做的事
- 分配负责人：根据上下文判断谁负责（如「张三去跟进」）
- 推断截止日期：根据上下文推断（如「下周之前」「月底前」）
- 判断优先级：根据讨论的紧迫程度和重要性
- 标注依赖关系：某个行动项是否依赖另一个完成
处理模糊情况
- 没有明确负责人 → 标注「待分配」
- 没有明确截止日期 → 标注「待定」
- 行动项不够具体 → 拆分为更小的可执行步骤
输出格式
## 行动项清单
**会议主题**：Q2 产品规划会
**日期**：2025-02-07
| # | 行动项 | 负责人 | 截止日期 | 优先级 |
|---|---|---|---|---|
| 1 | 完成 XX 功能需求文档 | 张三 | 2/14 | 🔴 高 |
| 2 | 收集 Beta 用户反馈 | 李四 | 2/12 | 🟡 中 |
| 3 | 联系设计外包团队报价 | 王五 | 2/10 | 🟡 中 |
| 4 | 更新项目排期表 | 待分配 | 待定 | 🟢 低 |
### 未决问题
- [ ] 是否需要增加服务器预算？（需要财务部门确认）
- [ ] 外包设计 vs 内部设计？（下次会议讨论）
输出规范
- 行动项要具体可执行（「调研」→「调研 XX 并输出对比报告」）
- 优先级用颜色标注，直观易读
- 未决问题单独列出，不混入行动项
- 如果用户需要，可以生成跟踪邮件模板
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 · 66 lines · 25 tokens per session scan A 94f193cb0650
meeting-notes-to-action-items is a skill published in the GitHub repository malue-ai/dazee-small (36 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 608 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-31.
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.