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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/health-check)<a href="https://agentmods.dev/commands/travisjneuman/.claude/health-check"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/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/travisjneuman/.claude/health-check"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/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.00009 | $0.00876 |
| Opus 5 | $0.00005 | $0.00438 |
| Sonnet 5 | $0.00002 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade C, and why
health-check scanned grade C with 2 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -c '"type": "command"' ~/.claude/settings.json Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
| `skills/` | 115+ items | `ls ~/.claude/skills/ \| wc -l` | How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Check
Comprehensive diagnostics for Claude Code toolkit.
Usage
/health-check [verbose]
Platform Compatibility
| Platform | Status | Notes |
|---|---|---|
| Windows | ✅ | Requires Git Bash (included with Git for Windows) |
| macOS | ✅ | Works with bash/zsh |
| Linux | ✅ | Works with bash |
All commands use POSIX-compatible syntax that works across platforms.
Behavior
Step 1: Configuration Check
Check settings.json:
# Cross-platform: works in Git Bash (Windows), bash (macOS/Linux)
[ -f ~/.claude/settings.json ] && echo "OK" || echo "MISSING"
Verify:
- File exists
- Valid JSON
- Hooks configured
- Permissions set
- MCP servers listed
Step 2: Structure Verification
Check directory structure:
| Directory | Expected | Check |
|---|---|---|
skills/ |
115+ items | ls ~/.claude/skills/ | wc -l |
agents/ |
86+ files | ls ~/.claude/agents/*.md | wc -l |
commands/ |
30+ files | ls ~/.claude/commands/*.md | wc -l |
templates/ |
5+ files | ls ~/.claude/templates/ | wc -l |
plugins/marketplaces/ |
108 repos | ls ~/.claude/plugins/marketplaces/ | wc -l |
Step 3: Hooks Status
Verify registered hooks:
grep -c '"type": "command"' ~/.claude/settings.json
Expected: 7+ hook commands across 5+ events (SessionStart, Stop, UserPromptSubmit, PreToolUse, PostToolUse, PreCompact)
Step 4: Git Status
Check submodules:
cd ~/.claude && git submodule status
Verify:
- All submodules initialized
- No detached heads
- No uncommitted 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.
- 9d ago First seen · 149 lines · 9 tokens per session scan C dfd946cc7ee4
health-check is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 876 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
performance-audit
Find performance bottlenecks across the stack — queries, rendering, bundle size, memory.
debug
Systematic debugging — reproduce, isolate, fix, verify, and add regression test.
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
build-fix
A build-error fixing procedure for TypeScript projects. It runs the project build, groups and explains errors, applies fixes one at a time, and checks the build again.
refactor-cleanup.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ui-bug.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.