Mooncake is a serving platform for Kimi, an LLM service from Moonshot AI, built around sharing and transferring the KV cache used during language-model inference. It supports disaggregated serving and data movement between inference, training, and rollout systems. The catalogue add-ons operate or integrate with Mooncake-based serving and transfer workflows.
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/kvcache-ai/MooncakeWrote 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/plugins/kvcache-ai/mooncake/mooncake-troubleshoot)<a href="https://agentmods.dev/plugins/kvcache-ai/mooncake/mooncake-troubleshoot"><img src="https://agentmods.dev/badge/plugins/kvcache-ai/mooncake/mooncake-troubleshoot/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/plugins/kvcache-ai/mooncake/mooncake-troubleshoot"><img src="https://agentmods.dev/badge/plugins/kvcache-ai/mooncake/mooncake-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mooncake-troubleshoot 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "mooncake-troubleshoot",
"description": "Systematically diagnose Mooncake deployment and runtime issues (services, RDMA, env vars, connectivity, logs) and propose fixes.",
"author": {
"name": "Mooncake Team"
},
"homepage": "https://kvcache-ai.github.io/Mooncake/skills/mooncake-troubleshoot.html",
"repository": "https://github.com/kvcache-ai/Mooncake",
"license": "Apache-2.0",
"keywords": ["mooncake", "troubleshooting", "rdma", "deployment"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 134 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 13 lines scan A 0200ab2c1166
mooncake-troubleshoot is a plugin published in the GitHub repository kvcache-ai/Mooncake (6,818 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
codeeraser
CodeEraser passive guard + erase skill: a winnowing clone index behind a per-project daemon intercepts T1/T2 duplicate writes at PreToolUse (with the tombstone and flow legs judged in the core), records at PostToolUse whether an asked write ran (settle), audits net LOC + touched duplicates at Stop, and reports health…
spine
Understand any codebase, then ship changes to it. Read-only comprehension tools (maprepo, blastradius, explainsymbol, investigate, localize, regressiongaps, rootcause, docsfor) hand you engineering decisions — what breaks if you change X, what's untested, where a ticket or bug lands, which docs describe it — from.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
code-analysis
Codebase analysis commands: query, select-files, and file-tree for exploring and understanding repositories.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.