mooncake-troubleshoot

A troubleshooting add-on for Mooncake, a system whose deployments can use RDMA, a high-speed network technology. It examines deployment and runtime problems involving services, environment variables, connectivity, RDMA, and logs, then proposes fixes.

In plain words
What is it for?
Use it to diagnose Mooncake deployment failures, service issues, RDMA problems, missing or incorrect environment variables, connectivity errors, and log-reported failures.
Why use it?
It gives a structured way to investigate whether a failure comes from configuration, networking, services, or runtime behavior instead of relying on guesswork.

Plugin for Claude Code

Install

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.

agentmods
npx agentmods add plugins/kvcache-ai/mooncake/mooncake-troubleshoot
Claude Code
/plugin marketplace add kvcache-ai/Mooncake
Clone the repo
git clone --depth 1 https://github.com/kvcache-ai/Mooncake

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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 yesterday.

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.

.claude/skills/mooncake-troubleshoot/.claude-plugin/plugin.json · 13 lines

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"]
}
Changes

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.

  1. yesterday First seen · 13 lines scan A 0200ab2c1166

Subscribe to this mod's changes

mooncake-troubleshoot is a plugin published in the GitHub repository kvcache-ai/Mooncake (6,438 stars, last pushed 2d ago), 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.