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-setup)<a href="https://agentmods.dev/commands/kimyx0207/kim_service/kim-setup"><img src="https://agentmods.dev/badge/commands/kimyx0207/kim_service/kim-setup/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-setup"><img src="https://agentmods.dev/badge/commands/kimyx0207/kim_service/kim-setup.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.00735 |
| Opus 5.5 | $0.00010 | $0.00294 |
| Sonnet 5.5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
kim-setup 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.
What it actually says
Kim Service 执行门（必须先执行）
- 先复述原始用户意图，并列出本次只读检测项；本命令不自动安装、不写 MCP 或用户级配置。
check只检测，plan只输出修复计划。需要项目级安装时，展示 kim-ccg plan 结果，必须由用户另行明确批准 apply。- 认证与代理只报告
configured或disabled，不得输出值、URL、端口、Token 或凭证。 - MCP 仅对应本 Tool 的
cli.mjs mcp codex与cli.mjs mcp gemini运行时；不要读取或创建仓库旧配置、用户目录会话文件或持久日志。
Kim环境检测命令
运行模式：$ARGUMENTS（默认 check）。除 check 和 plan 外拒绝执行。
1. 基础与 CLI 检测
只运行版本/存在性检查：
node --version
claude --version
codex --version
gemini --version
如果宿主环境无法直接启动 npm shim，报告 installed but host launch unresolved，不要改 PATH、执行策略或用户配置。
2. MCP 注册状态
从当前宿主的 MCP 工具列表检查 mcp__codex__codex 与 mcp__gemini__gemini。不要通过读取某个固定配置文件推断已注册。
若缺失，输出如下计划，不执行：
- 定位 Kim Service 中本组件的绝对路径。
- Codex server command:
node <component>/cli.mjs mcp codex。 - Gemini server command:
node <component>/cli.mjs mcp gemini。 - 由用户在实际 MCP 宿主中添加配置并重启宿主。
3. 认证与代理状态
只检查是否配置，输出示例：
OPENAI_API_KEY status: configured|disabled
GEMINI_API_KEY status: configured|disabled
HTTP proxy forwarding: configured|disabled
HTTPS proxy forwarding: configured|disabled
不得回显任何变量值。代理默认不转发；只有操作员显式设置 KIM_CCG_FORWARD_PROXY=1 时，运行时才会验证并转发无凭证 HTTP(S) 代理 URL。
4. 项目级宿主资产
需要安装 Claude commands/Skill 时，先运行 dry-run：
node <component>/cli.mjs install --target <project-root>
展示目标文件、冲突和哈希。用户明确批准项目写入后，才可建议：
node <component>/cli.mjs install apply --target <project-root> --confirm-project-write
冲突文件默认拒绝；不得自动添加 --replace。
5. 输出
按 ready / partial / blocked 汇总 Node、Claude、Codex、Gemini、两项 MCP 注册、认证状态与代理转发状态。修复计划必须与检测结果分开，且不得声称已经执行。
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 · 74 lines · 25 tokens per session scan A f3035917d511
kim-setup is a command published in the GitHub repository KimYx0207/Kim_Service (177 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 735 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.