Borrowing it
Nothing to install: this file belongs to opensesh/karimo-overview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensesh/karimo-overview/main/.claude/commands/test-mcp.mdgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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/opensesh/karimo-overview/test-mcp)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/test-mcp"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/test-mcp.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.00007 | $0.02336 |
| Opus 5 | $0.00003 | $0.01168 |
| Sonnet 5 | $0.00001 | $0.00467 |
| Haiku 4.5 | $0.00001 | $0.00234 |
Grade A, and why
test-mcp 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Verify the base URL is reachable with a quick `curl -s -o /dev/null -w "%{http_code}" {BASE_URL}` How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run an automated test suite against the BOS MCP server. This validates environment, authentication, all 10 tools, the resource endpoint, asset proxy, and error sanitization.
Setup
-
Determine the base URL:
- If the dev server is running:
http://localhost:3000 - Otherwise use
NEXT_PUBLIC_APP_URLorhttps://bos-3-0.vercel.app - Verify the base URL is reachable with a quick
curl -s -o /dev/null -w "%{http_code}" {BASE_URL}
- If the dev server is running:
-
Get the MCP API key:
- Check if
MCP_TEST_API_KEYenv var is set - If not, ask the user for their MCP API key (generated in BOS settings)
- Check if
-
Initialize results tracking:
- Track pass/fail/skip counts
- Store failure details for summary
Test Execution
Run tests sequentially. For each test, report the result inline: PASS, FAIL (with reason), or SKIP (with reason).
Phase 1: Environment Check
Check that required env vars are set (read their existence, not their values):
# Check each var exists (non-empty)
[ -n "$NEXT_PUBLIC_SUPABASE_URL" ] && echo "PASS: NEXT_PUBLIC_SUPABASE_URL" || echo "FAIL: NEXT_PUBLIC_SUPABASE_URL not set"
[ -n "$SUPABASE_SERVICE_ROLE_KEY" ] && echo "PASS: SUPABASE_SERVICE_ROLE_KEY" || echo "FAIL: SUPABASE_SERVICE_ROLE_KEY not set"
[ -n "$OPENAI_API_KEY" ] && echo "PASS: OPENAI_API_KEY" || echo "FAIL: OPENAI_API_KEY not set"
Phase 2: Auth Flow
Test authentication against the MCP endpoint:
# A1: No token - expect 401
curl -s -o /dev/null -w "%{http_code}" -X POST {BASE_URL}/api/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'
# A2: Invalid token - expect 401
curl -s -o /dev/null -w "%{http_code}" -X POST {BASE_URL}/api/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer fake_invalid_token_xyz" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'
# A3: Valid token - expect 200
curl -s -o /dev/null -w "%{http_code}" -X POST {BASE_URL}/api/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {API_KEY}" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'
# A5: OAuth metadata
curl -s -o /dev/null -w "%{http_code}" {BASE_URL}/.well-known/oauth-authorization-server
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 · 204 lines · 7 tokens per session scan A e3eb7a528492
test-mcp is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 2,336 once invoked, about $0.0000 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-30.
Other commands, from other repositories
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
develop
Implement skill development issues with TDD-governed workflow.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.