Borrowing it
Nothing to install: this file belongs to jamesbrink/mcp-deadmansnitch. 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/jamesbrink/mcp-deadmansnitch/main/.claude/commands/test-mcp-tools.mdgit clone --depth 1 https://github.com/jamesbrink/mcp-deadmansnitchWrote 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/jamesbrink/mcp-deadmansnitch/test-mcp-tools)<a href="https://agentmods.dev/commands/jamesbrink/mcp-deadmansnitch/test-mcp-tools"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-deadmansnitch/test-mcp-tools/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/jamesbrink/mcp-deadmansnitch/test-mcp-tools"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-deadmansnitch/test-mcp-tools.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.00000 | $0.00949 |
| Opus 5 | $0.00000 | $0.00475 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
test-mcp-tools 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.
- **ONLY use the MCP tools** - Do NOT use curl, bash commands, or direct API calls How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Test Plan
- List all snitches - Use the MCP tool to list existing snitches and display a summary
- Create a test snitch - Create a new snitch with specific test parameters
- Get snitch details - Retrieve and display the created snitch's details
- Update the snitch - Modify various attributes of the test snitch
- Add tags - Add multiple tags to the test snitch
- Remove a tag - Remove one of the added tags
- Check in - Send a check-in to the test snitch with a message
- Pause the snitch - Temporarily pause monitoring
- Unpause the snitch - Resume monitoring
- Delete the test snitch - Clean up by removing the test snitch
Important Instructions
- ONLY use the MCP tools - Do NOT use curl, bash commands, or direct API calls
- Use the unified snitch tool
mcp__deadmansnitch__snitchwith theactionparameter - Report each step's outcome clearly with success/failure status
- If any step fails, continue with the remaining tests and note the failure
- Use unique identifiers for the test snitch to avoid conflicts
Test Execution
Step 1: List All Snitches
Use mcp__deadmansnitch__snitch with action="list" to get the current list of snitches. Display:
- Total count of snitches
- A brief summary of existing snitches (names and statuses)
Step 2: Create Test Snitch
Use mcp__deadmansnitch__snitch with these parameters:
- action: "create"
- name: "MCP Tool Test Snitch - DELETE ME"
- interval: "hourly"
- notes: "This is a temporary test snitch created to verify MCP tools functionality. Safe to delete."
- alert_type: "basic"
Save the token from the response for subsequent operations.
Step 3: Get Snitch Details
Use mcp__deadmansnitch__snitch with:
- action: "get"
- token: (from Step 2)
Step 4: Update Snitch
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 · 120 lines · 0 tokens per session scan A c383aad7012f
test-mcp-tools is a command published in the GitHub repository jamesbrink/mcp-deadmansnitch (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 949 tokens. 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
compare
Compare the FIBER compiler against equal-engineering baselines (graph walks, lexical retrieval) and report which preserve the reference verdict.
generate
Generate maintainable pytest tests from a URL or mobile screen via mk-qa-master's analyzer.
run-tests
Run a focused subset of the user's test suite via mk-qa-master, surface failures, and offer next steps.
multi-page
Smoke test multiple pages in parallel using alethiatellparallel.
smoke
Quick Alethia smoke test — navigate and assert the page loads.
checklist
Generate a custom checklist for the current feature based on user requirements.