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 vamshisuram/cc-manager/plugin install cc-managerWrote 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/commands/vamshisuram/cc-manager/doctor)<a href="https://agentmods.dev/commands/vamshisuram/cc-manager/doctor"><img src="https://agentmods.dev/badge/commands/vamshisuram/cc-manager/doctor/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/commands/vamshisuram/cc-manager/doctor"><img src="https://agentmods.dev/badge/commands/vamshisuram/cc-manager/doctor.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00265 |
| Opus 5 | $0.00005 | $0.00133 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
doctor scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:4178/api/state What it actually says
Give the user a quick read on their Claude Code setup without opening the browser.
If the server is already running on http://localhost:4178, fetch state from it:
curl -s http://localhost:4178/api/state
If it's not running, spin one up briefly:
NO_OPEN=1 node "${CLAUDE_PLUGIN_ROOT}/server.mjs" &
SVR=$!
sleep 1
STATE=$(curl -s http://localhost:4178/api/state)
kill $SVR 2>/dev/null
Then summarize in compact terminal-friendly form:
<N>plugins, top 3 by command count<N>slash commands,<N>subagents,<N>skills<N>hooks total — call out any withhealth: "broken"(with their event and script path)<N>MCP servers — list disconnected ones- All
conflicts[]entries (title + detail) - Sessions: total, total messages, top 3 most-active projects
End with: "Open the full UI with /cc-manager:open."
Keep the output dense and scannable. No prose paragraphs.
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.
- 9d ago First seen · 35 lines · 11 tokens per session scan A 1ca19355321a
doctor is a command published in the GitHub repository vamshisuram/cc-manager (10 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 265 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.