Borrowing it
Nothing to install: this file belongs to shenjingnan/xiaozhi-client. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shenjingnan/xiaozhi-client/main/.agents/skills/todo-manager/SKILL.mdgit clone --depth 1 https://github.com/shenjingnan/xiaozhi-clientWrote 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/shenjingnan/xiaozhi-client/todo-manager)<a href="https://agentmods.dev/skills/shenjingnan/xiaozhi-client/todo-manager"><img src="https://agentmods.dev/badge/skills/shenjingnan/xiaozhi-client/todo-manager/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/shenjingnan/xiaozhi-client/todo-manager"><img src="https://agentmods.dev/badge/skills/shenjingnan/xiaozhi-client/todo-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.01286 |
| Opus 5 | $0.00010 | $0.00643 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
todo-manager 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 12d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
我是 Todo Manager，专门负责管理 xiaozhi-client 项目架构演进过程中的待办事项。
为什么会有 Todo
在软件架构演进过程中，新老架构共存是必然现象。我们无法在单个 PR 中完成所有改动，因此需要通过多个 PR 逐步迭代。这些跨 PR 的任务需要被妥善记录和管理。
Todo 存在的原因
- 架构迁移需要分阶段进行：新旧架构需要在一段时间内共存
- 向后兼容性要求：在完全迁移前，旧代码需要保留以保持兼容性
- 风险控制：大规模改动风险高，需要分步验证
- 团队协作：不同开发者可能负责不同阶段的任务
- 知识传递：待办事项文档是技术决策的载体
Todo vs Issue
| Todo 文档 | Issue |
|---|---|
| 存储在代码仓库中 | 存储在 GitHub 上 |
| 关注技术细节和实现方法 | 关注用户价值和功能需求 |
| 用于架构演进记录 | 用于功能跟踪和讨论 |
| 包含详细的技术上下文 | 通常是高层描述 |
技能能力
1. 创建 Todo 文档
通过 /todo <标题> 命令创建新的待办事项。
2. 查看所有 Todo
请列出 todos 目录下的所有待办事项，按创建时间排序
3. 搜索特定 Todo
请搜索包含"连接管理"关键词的 todo 文档
请搜索影响 src/server/services/ 目录的所有 todo
4. 评估 Todo 优先级
请评估当前所有 todo 的处理优先级，考虑：
- 阻塞其他任务的程度
- 技术债务的严重性
- 处理的复杂度
5. 检查 Todo 状态
请检查是否有 todo 的处理条件已满足（如相关 PR 已合并）
使用方法
查看所有待办事项
请帮我列出 todos 目录下的所有待办事项，并简要说明每个 todo 的状态
评估某个 Todo 是否可以处理
我正在处理端点迁移工作，请帮我检查有哪些 todo 现在可以处理了
更新 Todo 文档
请更新 todos/2025-01-23-refactor-connection-manager.md，添加以下信息：
- 相关 PR #595 已合并
- 预计在下一个版本处理
关闭已完成的 Todo
todos/2025-01-23-refactor-connection-manager.md 已完成，请将其归档或标记为已完成
Todo 文档最佳实践
1. 清晰的背景说明
## 背景
在独立架构迁移（#590）中，我们需要逐步将各个端点从旧的负载均衡架构迁移到独立架构。这个 todo 涉及迁移最后一个端点。
2. 明确的 Todo 原因
## 为什么 Todo
- 旧代码仍有其他模块依赖
- 需要等待所有端点迁移完成
- 当前阶段需要保持向后兼容
3. 可判断的处理时机
## 合适的处理时机
- 所有端点都已迁移到独立架构
- 没有代码引用旧的 LoadBalancer 类
- 相关测试已更新
4. 详细的处理方法
## 正确的处理方法
1. 确认没有代码引用 LoadBalancer
2. 删除 src/server/services/LoadBalancer.ts（如存在）
3. 更新相关导入语句
4. 运行 pnpm check:all 验证
5. 提交 PR 并关联此 todo
5. 准确的影响范围
## 影响范围
- src/server/services/LoadBalancer.ts（删除）
- src/server/services/MCPServiceManager.ts（更新导入）
- 对应的测试文件（删除）
验证检查清单
创建或更新 Todo 文档时，确保：
- 背景信息清晰完整
- Todo 原因明确具体
- 处理时机有明确的判断标准
- 处理方法详细可执行
- 影响范围准确列出
- 文件命名符合规范（YYYY-MM-DD-kebab-title.md）
- 包含创建时间和更新记录
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.
- 12d ago First seen · 182 lines · 19 tokens per session scan A 34821249ff50
todo-manager is a skill published in the GitHub repository shenjingnan/xiaozhi-client (338 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 1,286 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.