agentmods.dev

health

A command that checks whether a Claude Code project is configured correctly, including its instructions, settings, hooks, rules, error log, secrets, and MCP server commands.

In plain words
What is it for?
Validating a Claude Code setup and producing warnings about configuration, security, or required tools that need attention.
Why use it?
It helps find missing files, invalid settings, non-executable hooks, possible secrets, and unavailable server commands before they cause problems.

Command for Claude Code

11 4mo ago A scan 14 tokens original MIT
View the source file brain-bootstrap/claude-code-brain-bootstrap
Install

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.

agentmods
npx agentmods add commands/brain-bootstrap/claude-code-brain-bootstrap/health
Clone the repo
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 484 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00484
Opus 5 $0.00007 $0.00242
Sonnet 5 $0.00003 $0.00097
Haiku 4.5 $0.00001 $0.00048

Measured 2d ago against content hash 654e0d697229, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

health 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 2d 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.

.claude/commands/health.md · 35 lines

What it actually says

Health Check — Configuration Validation

Verify that the Claude Code configuration is healthy and complete.

Steps

  1. CLAUDE.md — verify it exists, is not empty, and contains key sections (Build, Stack, Architecture, Conventions)
  2. settings.json — verify .claude/settings.json exists and is valid JSON (jq . .claude/settings.json)
  3. Hooks — verify all .claude/hooks/*.sh files exist and are executable (test -x)
  4. Rules frontmatter — verify all .claude/rules/*.md files have globs: or paths: in frontmatter (except _template* and domain/_template*)
  5. Error log — verify claude/tasks/CLAUDE_ERRORS.md exists (warn if missing)
  6. Secrets scan — grep for common secret patterns in tracked files: 
    git ls-files | xargs grep -l 'BEGIN.*PRIVATE KEY\|password\s*=\s*["\x27][^"\x27]\{8,\}' 2>/dev/null | head -10
    Report any matches as ⚠️ warnings
  7. MCP server binaries — verify each server declared in .mcp.json has its binary in PATH: 
    jq -r '.mcpServers | to_entries[] | "\(.key):\(.value.command)"' .mcp.json 2>/dev/null || echo "NO_MCP_JSON"
    For each key:command pair, run command -v <command> and report ✅/⚠️. Known binary mapping for this project:
    • codebase-memory-mcp → binary codebase-memory-mcp
    • cocoindex-code → binary ccc
    • code-review-graph → binary uvx (via uv/pipx runner) Any missing binary means that MCP server is silently unavailable to Claude.
  8. Report — summarize: ✅ healthy / ⚠️ warnings / ❌ problems with actionable fixes
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.

  1. 2d ago First seen · 35 lines · 14 tokens per session scan A 654e0d697229

Subscribe to this mod's changes

health is a command published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 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.

Securityclaude-codeclaude-configclaude-context
Related

Other commands, from other repositories

restart

Restart the claude-mnemonic worker process. Use this command when experiencing issues with the memory system.

lukaszraczylo/claude-mnemonic · 0 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens