agentmods.dev

mcp-coroot: Command for Claude Code

.claude/commands/coroot-smoke.md

coroot-smoke is a command for Claude Code from jamesbrink/mcp-coroot. It costs 0 tokens per session (346 once invoked), scanned A, original, MIT.

A read-only health check for a configured Coroot instance, including its projects, applications, nodes, alerts, traces, metrics, deployments, costs, and integrations.

In plain words
What is it for?
It is for testing access, checking monitoring components such as ClickHouse, and producing a broad status report from the first available project.
Why use it?
It checks whether the monitoring connection and its supporting services work before relying on their results. It does not change Coroot.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is jamesbrink/mcp-coroot's own configuration. It tells Claude Code how to work on mcp-coroot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-coroot configures →

not rated 16repo 1mo ago A scan 0 tokens original MIT
View source ↗ jamesbrink/mcp-coroot
Reuse

Borrowing it

Nothing to install: this file belongs to jamesbrink/mcp-coroot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jamesbrink/mcp-coroot/main/.claude/commands/coroot-smoke.md
Clone the repo
git clone --depth 1 https://github.com/jamesbrink/mcp-coroot

Made for: Claude Code.

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

agentmods badge for coroot-smoke

README.md
[![agentmods](https://agentmods.dev/badge/commands/jamesbrink/mcp-coroot/coroot-smoke/github.svg)](https://agentmods.dev/commands/jamesbrink/mcp-coroot/coroot-smoke)
Your own site
<a href="https://agentmods.dev/commands/jamesbrink/mcp-coroot/coroot-smoke"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-coroot/coroot-smoke/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.

agentmods 80×15 button for coroot-smoke

Your own site · 80×15
<a href="https://agentmods.dev/commands/jamesbrink/mcp-coroot/coroot-smoke"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-coroot/coroot-smoke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00346
Opus 5.5 $0.00000 $0.00138
Sonnet 5.5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00035

Measured 1mo ago against content hash b1cb1d61a90a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coroot-smoke 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.

.claude/commands/coroot-smoke.md · 26 lines

What it actually says

Smoke test the Coroot MCP server

Exercise the read-only tools against the configured Coroot instance and report what works. Nothing here modifies Coroot.

  1. Call health_check. If it fails, stop and report the connection settings it returned.
  2. Call whoami and note the role, since it decides which tools can succeed.
  3. Call list_projects. Use the first project for everything below.
  4. Call get_project_status. Note whether the metrics source, node agent and ClickHouse are healthy: logs and traces need ClickHouse.
  5. Call list_applications. Note the status distribution and pick one application, preferring one at warning or critical.
  6. For that application call get_application, then get_log_patterns.
  7. Call list_nodes, and get_node for the first one.
  8. Call list_incidents and list_alerts. If either returns something, open the first with get_incident or get_alert.
  9. Call get_traces. If it reports no ClickHouse, note that and move on.
  10. Call list_metrics with match up.*, then get_metrics with query up.
  11. Call list_deployments, list_risks and get_costs.
  12. Call list_integrations, list_inspections and list_dashboards.

Report a table of tool, outcome and one line of detail. For failures, give the error message verbatim. Finish with whether the server looks healthy, and call out anything that failed for a reason other than missing data.

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. 1mo ago First seen · 26 lines · 0 tokens per session scan A b1cb1d61a90a

Subscribe to this mod's changes

coroot-smoke is a command published in the GitHub repository jamesbrink/mcp-coroot (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 346 tokens. 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-09-28.

Analytics and metricsDebuggingapmclaude-desktopcorootmcpmetricsmodel-context-protocol
Related

coroot-smoke compared with commands from other repositories

coroot-smoke next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
coroot-smokejamesbrink/mcp-corootCommand161mo agoMITA0Claude Code
vs-doctormtarcure/claude-vibe-squadCommand2289d agoMITA0Claude Code
preflightcdeust/CortexCommand76yesterdayMITA20Claude Code
umt-doctorMarkgatcha/universal-mcp-toolkitCommand163d agoMITA16Claude Code
fixHimanshu507/cgconeCommand9yesterdayMITA15Claude Code
wiki-linttboome33/obsidian-mcp-routerCommand15d agoApache-2.0A42Claude Code
foldicloudza/algokiller-pluginCommand805mo agoMITA37Claude Code