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/KimYx0207/Kim_ServiceWrote 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/kimyx0207/kim_service/kim-plan)<a href="https://agentmods.dev/commands/kimyx0207/kim_service/kim-plan"><img src="https://agentmods.dev/badge/commands/kimyx0207/kim_service/kim-plan/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/commands/kimyx0207/kim_service/kim-plan"><img src="https://agentmods.dev/badge/commands/kimyx0207/kim_service/kim-plan.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.00027 | $0.01362 |
| Opus 5.5 | $0.00011 | $0.00545 |
| Sonnet 5.5 | $0.00005 | $0.00272 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
kim-plan 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 1mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kim Service 执行门（必须先执行）
- 先复述原始用户意图，并列出本次计划调用的 MCP 工具、目标目录和拟新增或修改的文件；不要把本命令扩展成 Router 或自动验收流程。
- 任何项目写入、依赖安装、外部访问或环境变更都必须先获得对应的人类批准。未批准时只分析并展示计划。
- 写入前读取现有目标；目标已存在时不得用重定向、空文件或整文件覆盖。只做受管更新，遇到冲突停止并展示差异。
- 新文件只能在已批准的项目根目录内安全创建；不得写用户级配置。MCP 仅使用本 Tool 的 cli.mjs mcp codex 或 cli.mjs mcp gemini 运行时及其已注册工具。
Kim需求拆解命令
把模糊的大需求拆解为清晰的任务列表，含子任务、依赖关系、执行顺序
你现在要拆解这个需求：$ARGUMENTS
适用场景：产品经理给了一个大需求，不知道从哪开始？用这个命令！
执行流程
阶段1：需求理解与澄清
首先分析用户的需求，识别：
- 核心目标：用户到底想要什么？
- 隐含需求：没说但应该有的功能
- 技术约束：框架、语言、性能要求
- 边界条件：什么不需要做
如果需求不够清晰，提出澄清问题：
🤔 需要澄清几个问题：
1. 用户认证方式：JWT还是Session？
2. 数据库选型：MySQL还是PostgreSQL？
3. 是否需要前端页面？
阶段2：任务拆解
将需求拆解为可执行的任务列表。
拆解原则：
- 每个任务2-4小时可完成
- 每个任务有明确的输入和输出
- 任务之间依赖关系清晰
- 优先级按照"先基础后上层"排列
输出格式：
## 📋 任务列表
### 🔴 P0 - 基础设施（必须先完成）
#### 任务1：数据库模型设计
- **描述**：设计User表结构，包含必要字段
- **输入**：需求文档
- **输出**：models.py文件
- **预计时间**：2小时
- **依赖**：无
- **执行命令**：`/kim-code "设计User模型，字段包括..."`
#### 任务2：数据库迁移
- **描述**：创建数据库迁移文件并执行
- **输入**：models.py
- **输出**：migration文件
- **预计时间**：30分钟
- **依赖**：任务1
### 🟡 P1 - 核心功能
#### 任务3：用户注册API
- **描述**：实现注册接口，含参数校验
- **输入**：User模型
- **输出**：/api/register端点
- **预计时间**：3小时
- **依赖**：任务1、任务2
- **执行命令**：`/kim-api "用户注册接口，参数..."`
#### 任务4：用户登录API
- **描述**：实现登录接口，返回JWT
- **输入**：User模型
- **输出**：/api/login端点
- **预计时间**：3小时
- **依赖**：任务3
### 🟢 P2 - 增强功能
#### 任务5：密码重置
- **描述**：实现密码重置流程
- **输入**：邮件服务配置
- **输出**：/api/reset-password端点
- **预计时间**：4小时
- **依赖**：任务4
---
## 📊 任务依赖图
\`\`\`
任务1 ──→ 任务2 ──→ 任务3 ──→ 任务4 ──→ 任务5
(模型) (迁移) (注册) (登录) (重置)
\`\`\`
## ⏱️ 时间估算
| 优先级 | 任务数 | 总时间 |
|--------|--------|--------|
| P0 | 2个 | 2.5小时 |
| P1 | 2个 | 6小时 |
| P2 | 1个 | 4小时 |
| **总计** | **5个** | **12.5小时** |
## 🚀 执行建议
1. **第一天**：完成P0任务（基础设施）
2. **第二天**：完成P1任务（核心功能）
3. **第三天**：完成P2任务（增强功能）+ 测试
## 📝 下一步
准备好开始了吗？运行以下命令：
\`\`\`bash
/kim-code "任务1的描述"
\`\`\`
使用示例
# 功能需求
/kim-plan "实现用户认证系统，包括注册、登录、忘记密码"
# 系统设计
/kim-plan "设计RBAC权限系统"
# 重构任务
/kim-plan "把单体应用拆成微服务"
# 模糊需求
/kim-plan "优化系统性能"
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.
- 1mo ago First seen · 162 lines · 27 tokens per session scan A 3e8b8619a6cc
kim-plan is a command published in the GitHub repository KimYx0207/Kim_Service (177 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 1,362 once invoked, about $0.0001 per session on Opus 5.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-14.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.