Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add xiaolai/cc-suite/plugin install cc-suiteWrote 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/skills/xiaolai/cc-suite/diagnose)<a href="https://agentmods.dev/skills/xiaolai/cc-suite/diagnose"><img src="https://agentmods.dev/badge/skills/xiaolai/cc-suite/diagnose.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.00042 | $0.00924 |
| Opus 5 | $0.00021 | $0.00462 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
diagnose 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose
Run the structured diagnostic engine and act on its report. Skill counterpart to /cc-suite:diagnose — both are thin wrappers around the same engine, scripts/diagnose.py, which owns every check, its classification, and its repair mapping. Do not re-implement checks here.
When to Use
- At the start of a session when bridge artifacts may be missing or stale
- After updating cc-suite to confirm the new version is wired as expected
- When
$audit,$audit-fix, or any$claude-*skill behaves unexpectedly
Workflow
Step 0: Resolve the plugin root
CLAUDE_PLUGIN_ROOT is set by Claude Code only — in a Codex or Antigravity session it is unset. Resolve the root from the bridged skills symlink (it points at <plugin-root>/skills/cc-suite):
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "$(readlink -f .claude/skills/cc-suite 2>/dev/null)")")}"
[ -d "${PLUGIN_ROOT}/scripts" ] || echo "! cannot resolve the cc-suite plugin root — run /cc-suite:bridge-skills from Claude Code first, or export CLAUDE_PLUGIN_ROOT"
Stop if it could not be resolved.
Step 1: Run the engine
python3 "${PLUGIN_ROOT}/scripts/diagnose.py" --json
The JSON: enabled_tools, checks[] (id, label, status, detail, fix{auto[], manual, restart_required}), summary. Statuses: healthy / issue (fixable) / info / expected_absent / manual / skipped. The engine honors the Enabled Tools selection — a deselected tool's absent artifacts are expected_absent, never issues. Add --boot-test for the network-dependent claude-octopus handshake (tests the version actually registered in .codex/config.toml) when delegation misbehaves.
Step 2: Report
Render the buckets in order — Issues, Manual action needed, Information, Healthy, Expected absent/Skipped — emitting Information even on the no-issues path. If there are no issues and nothing manual: report healthy and stop.
Step 3: Fix
Ask: "Fix all auto-fixable issues now? (yes / show commands only / cancel)". If yes, for each issue check run its fix.auto commands in order; a non-zero exit is reported verbatim and that check is NOT counted as fixed. The model_pin fix is an edit, not a command: rewrite the - **Default model**: line in .cc-suite.md to latest and touch nothing else. fix.manual and manual-status items go to the user's to-do list untouched.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 65 lines · 42 tokens per session scan A b0f2f6a7032b
diagnose is a skill published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 4d ago), licensed ISC. It adds 42 tokens to every session and 924 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.