agentmods.dev

test-coroot-tools

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

A command for testing all available Coroot MCP tools directly. Coroot is a monitoring system that shows application health, infrastructure resources, logs, deployments, and distributed request traces.

In plain words
What is it for?
Use it for a structured Coroot integration test: verify health and login, inspect projects and applications, review infrastructure and traces, and create and verify a uniquely named test project.
Why use it?
It checks whether the tools, connection, authentication, and returned data work together, while avoiding changes to existing resources.

Command for Claude Code

Written for Claude Code: installed under .claude/.

not rated 16 yesterday A scan 0 tokens original MIT
View the source file jamesbrink/mcp-coroot
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 commands/jamesbrink/mcp-coroot/test-coroot-tools
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 test-coroot-tools

README.md
[![agentmods](https://agentmods.dev/badge/commands/jamesbrink/mcp-coroot/test-coroot-tools.svg)](https://agentmods.dev/commands/jamesbrink/mcp-coroot/test-coroot-tools)
Your own site
<a href="https://agentmods.dev/commands/jamesbrink/mcp-coroot/test-coroot-tools"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-coroot/test-coroot-tools.svg" alt="Measured on agentmods" 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 1,325 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.01325
Opus 5 $0.00000 $0.00662
Sonnet 5 $0.00000 $0.00265
Haiku 4.5 $0.00000 $0.00133

Measured 6d ago against content hash 26cc18913658, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

test-coroot-tools 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 6d 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/test-coroot-tools.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Coroot MCP Tools

Execute a comprehensive test of all Coroot MCP tools in a safe, non-destructive manner.

Test Sequence

  1. Health Check

    • Use the health_check tool to verify Coroot server connectivity

  2. Authentication Verification

    • Use the get_current_user tool to verify authentication is working

  3. Project Discovery

    • Use the list_projects tool to list all available projects
    • If projects exist, use the get_project tool on the first project
    • Use the get_project_status tool to check project health

  4. Create Test Project

    • Use the create_project tool to create a new project named mcp-test-{timestamp}
    • Use the get_project tool to verify the project was created

  5. Applications Overview

    • Use the get_applications_overview tool on an existing project
    • If applications exist, use the get_application tool on the first application

  6. Infrastructure Overview

    • Use the get_nodes_overview tool to view infrastructure nodes
    • Use the get_traces_overview tool to view distributed tracing summary
    • Use the get_deployments_overview tool to view deployment history

  7. Application Deep Dive (if applications exist)

    • Use the get_application_logs tool to retrieve recent logs
    • Use the get_application_traces tool to view traces

  8. Integrations

    • Use the list_integrations tool to view all configured integrations
    • Use the configure_integration tool to set up a test webhook integration

  9. Configuration Management

    • Use the list_inspections tool to view available inspection types
    • Use the get_application_categories tool to view current app categories
    • Use the create_application_category tool to create a test category
    • Use the update_application_category tool to update the test category
    • Use the delete_application_category tool to remove the test category
    • Use the get_custom_applications tool to view custom app definitions
    • If applications exist:
      • Use the get_inspection_config tool to get inspection configuration for an app
      • Use the update_inspection_config tool to test updating a configuration (with same values)
    • Use the update_custom_applications tool to test custom app updates (optional)

Read the full file on GitHub · 122 lines

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. 6d ago First seen · 122 lines · 0 tokens per session scan A 26cc18913658

Subscribe to this mod's changes

test-coroot-tools is a command published in the GitHub repository jamesbrink/mcp-coroot (16 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,325 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-08-30.

Testingapmclaude-desktopcorootmcpmetricsmodel-context-protocol
Related

Other commands, from other repositories

graph-report

Governance metrics dashboard — coverage by category, cross-reference density, compliance readiness, and project comparison across all working projects.

tractorjuice/arckit-claude · 23 tokens

test-mcp-tools

You are going to comprehensively test the Dead Man's Snitch MCP tools in a non-destructive manner. Follow these steps exactly and report the results of each operation.

jamesbrink/mcp-deadmansnitch · 0 tokens

monitor-health-check

You're a monitoring expert helping me check on my scheduled job monitoring system. I need you to do a comprehensive health check of my monitoring setup.

jamesbrink/mcp-deadmansnitch · 0 tokens

memcord-save-progress

Auto-summarize and save conversation progress.

ukkit/memcord · 8 tokens

validate-prd

Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.

agentkitai/agentlens · 23 tokens

editorial-review-structure

Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.

agentkitai/agentlens · 21 tokens