Borrowing it
Nothing to install: this file belongs to caidish/instrMCP. 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/caidish/instrMCP/main/.claude/commands/test_helper.mdgit clone --depth 1 https://github.com/caidish/instrMCPWrote 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/caidish/instrmcp/test_helper)<a href="https://agentmods.dev/commands/caidish/instrmcp/test_helper"><img src="https://agentmods.dev/badge/commands/caidish/instrmcp/test_helper/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/caidish/instrmcp/test_helper"><img src="https://agentmods.dev/badge/commands/caidish/instrmcp/test_helper.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.00009 | $0.01138 |
| Opus 5.5 | $0.00004 | $0.00455 |
| Sonnet 5.5 | $0.00002 | $0.00228 |
| Haiku 4.5 | $0.00001 | $0.00114 |
Grade A, and why
test_helper 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 2mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Interactive Test Helper
You are helping the user interactively test the InstrMCP server. You are presumably already connected to a user-launched instrmcp session, and in unsafe mode.
Context
- Server metadata: @instrmcp/config/metadata_baseline.yaml
- The user is running the MCP server in unsafe mode with consent dialogs
- Test notebook: "TestNotebook.ipynb" is open in JupyterLab
- You need to interact with instrmcp, and print the tool result to screen for the user to be able to verify it.
Test Categories
The user can specify a category to test: $ARGUMENTS
Available categories:
all- Test everything systematicallycore- Test mcp_list_resources, mcp_get_resourcenotebook- Test notebook_* tools (safe and unsafe)qcodes- Test qcodes_* toolsmeasureit- Test measureit_* toolsdatabase- Test database_* toolsresources- Test all resource templates
If no category specified, test all.
Testing Workflow
For each tool/resource category, follow this workflow:
1. Description Review
First, read the tool description from metadata_baseline.yaml and ask:
Use AskUserQuestion to ask:
"For [tool_name]: Is this description clear and accurate?"
Options:
- "Yes, clear and accurate"
- "Needs improvement" (ask for details)
- "Skip this tool"
2. Tool Execution Test
If the description is approved, attempt to call the tool with sensible defaults:
- For read-only tools: Execute directly and report results
- For unsafe tools: Warn the user that consent dialog will appear, then execute
- For tools requiring specific state (e.g., running sweep): Ask user to set up the state first
- For testing some of the tools, you may need to ask the user to run some code, or you use MCP to run code.
3. Result Verification
After execution, ask the user to verify:
Use AskUserQuestion to ask:
"Did [tool_name] behave as expected?"
Options:
- "Yes, working correctly"
- "Bug found" (document the issue)
- "Unexpected behavior" (document details)
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.
- 2mo ago First seen · 140 lines · 9 tokens per session scan A 173305b341f8
test_helper is a command published in the GitHub repository caidish/instrMCP (38 stars, last pushed 24d ago), licensed MIT. It adds 9 tokens to every session and 1,138 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
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…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.