A configuration checker for the Badi system. It examines files, hooks, permissions, and settings, then produces a diagnostic report.

Use it to verify hook scripts, check that settings.json is valid, and confirm referenced components exist and can run.

It finds missing files, invalid settings, broken references, and permission problems that can make Badi behave incorrectly. Run it after installation or when something goes wrong.

doctor — Command for Claude Code by fatihkan

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.

Clone the repo

git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/doctor.svg)](https://agentmods.dev/commands/fatihkan/badi/doctor)

Your own site

<a href="https://agentmods.dev/commands/fatihkan/badi/doctor"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/doctor.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 648 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00648
Opus 5	$0.00000	$0.00324
Sonnet 5	$0.00000	$0.00130
Haiku 4.5	$0.00000	$0.00065

Measured yesterday against content hash 6e2176e3e62e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

doctor 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 yesterday.

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/doctor.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Badi configuration validation. Checks all Badi components and produces a diagnostic report.

Required Tools

Bash (file permissions, directory structure checks)
Read (configuration and manifest files)
Glob (file existence scan)
...

Purpose

This command verifies that the Badi system is configured correctly. Recommended after a fresh install or whenever problems occur.

Check 1: Hook Scripts

Step 1: Hook File Presence

Scan the .claude/hooks/ directory
List all .sh and .js files
Verify the expected hooks exist:
- Pre-commit hook
- Post-commit hook
- Pre-push hook (if any)
- Custom Badi hooks

Step 2: Execute Permissions

Check the execute permission of every hook file (chmod +x)
Give a WARNING for files lacking permission
Check the shebang line (#!/bin/bash or #!/usr/bin/env node)
...

Check 2: settings.json Validation

Step 3: File Presence and Format

Check that .claude/settings.json exists
Verify the JSON format is valid (parseable)
FAIL on an empty or missing file

Step 4: Hook References

Read the hook definitions inside settings.json
Verify every referenced hook file physically exists
FAIL on broken references (hook entries without files)
...

Check 3: Agent Files

Step 5: Agent Directory Scan

Scan the .claude/agents/ directory
List all .md files

Step 6: Frontmatter Validation

For each agent file:

Check whether valid frontmatter exists at the top
Required fields: name, description (or a first-line description)
Verify tool definitions are in a valid format
...

Check 4: Command-Index References

Step 7: Read the Index File

Find and read command-index.md
Extract all command references listed in the index

Step 8: Reference Matching

Check that every index entry has a corresponding file under .claude/commands/
Detect files under commands/ that are missing from the index
Mark index entries without files as FAILED
...

Read the full file on GitHub · 109 lines

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.

yesterday First seen · 109 lines · 0 tokens per session scan A 6e2176e3e62e

Subscribe to this mod's changes

doctor is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 648 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-09-06.

Debugging agents ai-workflow cli developer-tools hooks

doctor