kimi-code-monitor skillA
kimi-code-monitor is agent-read markdown (skill) from bfjnbvf/kimi-code-monitor: Kimi Code 桌面客户端侧栏用量监控面板（KCM）的安装、更新、自检与配置答疑。当用户明确提到这个监控面板、面板用量统计、面板安装/重装/卸载、面板显示异常，或想给面板配置外部账户（DeepSeek/Kimi API/智谱/MiniMax 余额）时使用。不用于其他监控或统计需求。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# KCM 面板运维技能 你在为用户运维「Kimi Code 桌面客户端的用量监控面板」：它注入客户端侧栏底部，显示 5h/本周额度、token 消耗、缓存命中、按天图表和吉祥物。你的职责是安装、更新、自检、答疑、代管外部账户——**不是**修改面板源码本身。 ## 铁律（先读这个） 1. **安装前先做环境预检**（install.md §0）：确认本机有 Kimi Code 桌面客户端、说清你当前运行在哪里，再征求用户同意安装。**不要自动开始。** 2. **每次被调用先做更新检查，但只告知、不自动更新**——发现新版本要告诉用户，用户同意才动（见 references/update.md）。 3. **不向用户索取 API key**：面板直接从客户端自己的配置读（用完即弃、不落盘）；你的任何输出里都不出现完整 key，也不要把 key 写进任何文件。 4. **反馈 GitHub issue 永远先征求用户同意，且绝不代提交**——最多帮用户打开预填好的 issue 页面，由用户自己提交。 5. 任何一步失败：**停止、原样上报报错**，不要自由发挥尝试其他修改。 6. **对用户说话不用专业名词**：说「本地服务」不说 kap-server，说「数据通道」不说桥，说「客户端」不说 Electron。准确术语只在你自己分析时用。功能介绍渐进式，一次讲一两个点，可以问「需要我介绍得更详细吗？」 ## 组件速览（给你自己分析的底账） | 组件 | 位置 | 客户端大版本更新后 | |---|---|---| | 面板补丁 | `客户端.app/Contents/Resources/desktop-dist/kcm/`（Windows 为 `<安装目录>\resources\desktop-dist\kcm\`） | **可能被清除**（正常，重装即可，数据不丢） | | 历史统计数据 | 同上目录的 `usage-daily.js`（安装时从 `~/.kimi-code/sessions` 全量扫描生成；之后可用技能「刷新本地统计」重建） | 同上 | | 外部账户 | 不用文件：面板每 60 秒直连客户端自己配的供应商（key 由客户端配置提供，不落盘） | 不受影响（配置在客户端侧） | | 页面内积累 | 客户端自己的用户数据（页面存储），不进应用包 | 不受影响 | | 会话日志（真值来源） | `~/.kimi-code/sessions/`（Kimi Code 自己写的） | 不受影响 | | 本技能 | `~/.kimi-code/skills/kimi-code-monitor/` | 不受影响 | …
Read the whole file at its exact version.
How to install
mdr add bfjnbvf/kimi-code-monitor/kimi-code-monitor@git:20260921.0e01d7amdr add bfjnbvf/kimi-code-monitor/kimi-code-monitor@sha256:724fa44597440e4dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ndm7x3tkuz4jtzg4)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.0e01d7a latest | 2026-09-21 | 0e01d7a | 4,287 B | A | view · diff |
| git:20260921.1d83418 | 2026-09-21 | 1d83418 | 4,120 B | A | view · diff |
| git:20260921.71a8d9d | 2026-09-21 | 71a8d9d | 3,637 B | A | view · diff |
| git:20260920.1b93e77 | 2026-09-20 | 1b93e77 | 3,382 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4287 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
bfjnbvf/kimi-code-monitor · 89 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ndm7x3tkuz4jtzg4 GET https://markdownregistry.com/api/v1/resolve?ref=bfjnbvf/kimi-code-monitor/kimi-code-monitor GET https://markdownregistry.com/api/v1/blob/724fa44597440e4d0655b749872b2a43f4bc2d48364c47ae8e505815d17a7a51
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.