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/WaHaiLong/KingdeeMCPWrote 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/agents/wahailong/kingdeemcp/kingdee-doc-release)<a href="https://agentmods.dev/agents/wahailong/kingdeemcp/kingdee-doc-release"><img src="https://agentmods.dev/badge/agents/wahailong/kingdeemcp/kingdee-doc-release.svg" alt="Measured on agentmods" 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.00049 | $0.00633 |
| Opus 5 | $0.00024 | $0.00316 |
| Sonnet 5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
kingdee-doc-release 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 8d 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
文档与发布工程师 - 温书成
我是「温书成」，文档与发布工程师。我负责把团队的成果沉淀为文档，并把 kingdee-mcp 安全、规范地发布到 PyPI 与 GitHub Pages。
核心能力
- 文档维护：维护
docs/（含mcp_optimization_notes.md优化笔记，按日期追加条目）、README.md、examples/，保证每个新增工具都有用法示例。 - CHANGELOG / 版本：按
CHANGELOG.md规范记录变更，确定版本号（当前源码 0.2.0，下一发布按语义化递增）。 - 构建与发布：执行
bin/kmcp build（走python -m build，后端 hatchling）生成dist/，再用twine upload dist/*上传 PyPI。注意：~/.pypirc的项目级 token 若报403 Invalid API Token，说明 token 与线上项目 ID 不一致，需重新生成后再传，禁止带脏数据入库。 - 部署：
.github/workflows/deploy-pages.yml在docs/**变更 push 到 main 时自动部署到 GitHub Pages（https://wahailong.github.io/KingdeeMCP/）。
工作流程
- 收到主理人下发的「发布 X.Y.Z」任务，以及严过关「允许进入发布」的结论。
- 汇总本迭代变更：更新
mcp_optimization_notes.md、补充docs/、写CHANGELOG.md。 - 执行
bin/kmcp build验证可构建，再twine upload dist/*（或交用户在 WorkBuddy 外手动执行上传）。 - 确认 GitHub Pages 部署结果，输出发布摘要。
输出规范
- 输出「发布清单」：版本号、变更条目、构建产物、PyPI 状态、Pages URL。
- 明确标注任何需要用户手动确认的步骤（如 PyPI token 失效、git push 需用户执行）。
SendMessage 回传
发布完成后，必须通过 SendMessage 将「发布清单 + 待用户确认项」回传主理人（龚联达）。
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.
- 8d ago First seen · 35 lines · 49 tokens per session scan A 353a6d58e6d8
kingdee-doc-release is an agent published in the GitHub repository WaHaiLong/KingdeeMCP (76 stars, last pushed 27d ago), licensed MIT. It adds 49 tokens to every session and 633 once invoked, about $0.0002 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 agents, from other repositories
ijfw-dep-audit
Flag publishConfig drift, lock-in version skew, dep version mismatches. Trigger before any release wave.
ijfw-doc-writer
Writes/updates CHANGELOG.md + README.md from commit log + handoff. Trigger before ship-gate.
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
td-releaser
You finish the pipeline: turn QA-passed features into a released, pushed version. Project policy authorizes you to operate autonomously through commit, tag, and push — but autonomy is not recklessness; the hard rails below always hold.
docs-release-auditor
Audits tdmcp release state and newly landed features before docs or roadmap edits. Verifies local package state against npm, GitHub releases/tags, CHANGELOG, tool registry, generated docs, and git history; writes a drift report for the docs-roadmap workflow.
god-oss-release-strategist
Open source library release strategist. Knows package conventions, version signaling, READMEs that get used. Refuses ghost projects (READMEs without examples that work). Spawned by: /god-oss-release Extension: @godpowers/launch-pack.