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/monitor-health-check.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/monitor-health-check)<a href="https://agentmods.dev/commands/jamesbrink/mcp-deadmansnitch/monitor-health-check"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-deadmansnitch/monitor-health-check/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/monitor-health-check"><img src="https://agentmods.dev/badge/commands/jamesbrink/mcp-deadmansnitch/monitor-health-check.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.00499 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
monitor-health-check 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 11d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Your Task
Please help me with the following monitoring tasks:
1. Check Current Monitors
First, I'd like to see what monitors I currently have set up. Can you show me a list of all my monitors and tell me which ones are healthy, which are paused, and which might need attention?
2. Set Up a Test Monitor
I need to set up a temporary monitor to test that everything is working properly. Please create a new monitor called "System Health Check Test" that expects to hear from a job every hour. Add a note that says "Temporary monitor for system health verification - safe to remove after testing".
3. Verify the Test Monitor
Once you've created it, please check that the test monitor was set up correctly by retrieving its details and confirming all the settings are correct.
4. Update Monitor Configuration
Actually, I think I want this test monitor to check in daily instead of hourly. Can you update it? Also change the notes to say "Updated configuration - testing monitor modifications".
5. Organize with Labels
Please add some labels to help organize this test monitor. Add these tags: "health-check", "automated-test", and "temporary".
6. Tag Cleanup
Actually, the "temporary" tag seems redundant. Can you remove just that one tag while keeping the others?
7. Test Check-in
Let's make sure the monitor is working by sending a test check-in. Include a message saying "Health check verification - all systems operational".
8. Maintenance Window
I need to pause this monitor for maintenance. Can you pause it for about an hour from now?
9. Resume Monitoring
Actually, let's resume monitoring right away - I don't need the maintenance window after all.
10. Cleanup
Since this was just a test, please remove this temporary monitor so it doesn't clutter my dashboard.
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.
- 11d ago First seen · 59 lines · 0 tokens per session scan A 1520f0101cd0
monitor-health-check 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 499 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-31.
Other commands, from other repositories
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.