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-team)<a href="https://agentmods.dev/commands/kimyx0207/kim_service/kim-team"><img src="https://agentmods.dev/badge/commands/kimyx0207/kim_service/kim-team/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-team"><img src="https://agentmods.dev/badge/commands/kimyx0207/kim_service/kim-team.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.00030 | $0.02165 |
| Opus 5.5 | $0.00012 | $0.00866 |
| Sonnet 5.5 | $0.00006 | $0.00433 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
kim-team 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kim-team — 86% identical, 86 lines differ
How it starts
The opening of the file, as written. The whole thing — 242 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团队协作命令(基于MCP)
公众号:老金带你玩AI | 微信:xun900207 | 备注AI加入AI交流群
你现在要协调3个AI工具完成任务:$ARGUMENTS
重要:本命令使用MCP Server封装的Codex和Gemini工具,而不是直接调用bash命令。
⚠️ 文件写入规则(必须遵守)
先展示 .kim-orchestrator/ 与实际代码的完整目标清单并获得项目写入批准。逐个读取已有目标并受管更新;新文件安全创建。禁止重定向、预创建空文件或静默覆盖。
执行流程
阶段0.1:健康检查
参考 .claude/skills/kim-orchestrator/prompts/health-check.md 执行MCP健康检查。
在开始前检测MCP工具是否可用:
- 检测
mcp__codex__codex(代码生成必需) - 检测
mcp__gemini__gemini(代码审查必需)
根据检测结果:
- ✅ 全部可用 → 继续执行完整流程
- ⚠️ Codex不可用 → 询问是否用Claude降级生成
- ⚠️ Gemini不可用 → 询问是否跳过审查(等同/kim-code)
- ❌ 全部不可用 → 显示修复指南,运行
/kim-setup
阶段0.2:初始化工作目录
在开始任何阶段前,先创建工作目录和所有需要的空文件:
批准后安全创建 .kim-orchestrator/,逐个检查四个目标文件;存在则读取,不存在才创建。
然后依次读取这些文件(可并行):
- Read .kim-orchestrator/phase1_requirements.json
- Read .kim-orchestrator/phase2_code.md
- Read .kim-orchestrator/phase3_review.md
- Read .kim-orchestrator/result.md
阶段1:需求分析(你自己完成)
请详细分析用户的需求,输出JSON格式的技术方案,包含:
{
"task_description": "任务描述",
"features": ["功能1", "功能2", "..."],
"tech_stack": {
"language": "编程语言",
"framework": "框架",
"libraries": ["依赖库1", "依赖库2"]
},
"file_structure": {
"files": [
{"path": "文件路径", "purpose": "用途"}
]
},
"key_points": [
"关键实现要点1",
"关键实现要点2"
],
"risks": [
"潜在风险1",
"潜在风险2"
]
}
将这个JSON保存到临时文件 .kim-orchestrator/phase1_requirements.json
阶段2:代码生成(调用Codex MCP Server)
使用MCP工具调用Codex生成代码。
重要:检查是否有 mcp__codex__codex 工具可用。如果没有,告诉用户:
⚠️ Codex MCP Server未配置!
请按照以下步骤配置:
1. 查看本组件 README 的 MCP 启动方式
2. 在实际 MCP 宿主注册 `node <component>/cli.mjs mcp codex`
3. 重启该 MCP 宿主
如果工具可用,调用Codex MCP Server:
请使用mcp__codex__codex工具生成代码,传入以下参数:
- prompt: 根据.kim-orchestrator/phase1_requirements.json的内容生成完整代码
- cwd: 当前已批准的项目根目录
- sandbox: 只有批准写入时使用 `workspace-write`
将Codex的响应保存到 .kim-orchestrator/phase2_code.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.
- 1mo ago First seen · 242 lines · 30 tokens per session scan A a860dc71586c
kim-team is a command published in the GitHub repository KimYx0207/Kim_Service (177 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 2,165 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
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
refactor
Systematic code refactoring with smart scope detection.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).