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.
npx skills add jhlee0409/all-for-claudecode --skill doctorgit clone --depth 1 https://github.com/jhlee0409/all-for-claudecodeWrote 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/skills/jhlee0409/all-for-claudecode/doctor)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/doctor"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/doctor/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/skills/jhlee0409/all-for-claudecode/doctor"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/doctor.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.00013 | $0.01040 |
| Opus 5 | $0.00006 | $0.00520 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
afc: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 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:doctor — Plugin Setup Diagnosis
Checks whether the all-for-claudecode plugin is correctly installed and configured in the current project. Like
brew doctororflutter doctor— verifies the tool's setup, NOT the project's code quality. Read-only — never modifies files. Reports issues with actionable fix commands.IMPORTANT: Do NOT analyze project source code, architecture, or code quality. Only check afc plugin configuration, hooks, state, and environment. All checks are handled by the bash script — just run it and print the output.
Arguments
$ARGUMENTS— (optional) flags:--verbose— detailed output with command results and file paths--fast— skip CI/gate command execution checks (faster)
Output Format
Three-tier status per check:
✓— pass (healthy)⚠— warning (non-blocking but suboptimal)✗— fail (broken, needs action)
Each failing check includes a Fix: line with the exact command to resolve it.
Execution
-
Run the health check script (covers ALL categories — no manual checks needed):
"${CLAUDE_SKILL_DIR}/../../scripts/afc-doctor.sh" $ARGUMENTS -
Print the script's stdout output as-is. Do not reformat, summarize, or interpret.
-
Stop. Output nothing after the script output. No analysis, no suggestions, no follow-up actions.
Rules:
- The ONLY Bash command you may run is the
afc-doctor.shscript above. No other Bash calls. - Do NOT execute Fix commands. They are for the user to run manually.
- Do NOT analyze project source code, git history, branches, or architecture.
Example Output
all-for-claudecode Doctor (v2.11.0)
Plugin root: /path/to/plugin
Environment
✓ git installed (2.43.0)
⚠ jq not found — hook scripts will use grep/sed fallback
Fix: brew install jq
Project Config
✓ .claude/afc.config.md exists
✓ Required sections present
✓ Gate command defined
CLAUDE.md Integration
✓ Global ~/.claude/CLAUDE.md exists
✓ all-for-claudecode block present
⚠ all-for-claudecode block outdated (block: 1.0.0, plugin: 1.1.0)
Fix: run /afc:setup to update
Legacy Migration
✓ No legacy artifacts found
Pipeline State
✓ No stale pipeline state
✓ No orphaned artifacts
Memory Health
Hook Health
✓ hooks.json valid
✓ All hook scripts exist
✓ All scripts executable
Learner Health
✓ Learner not enabled (opt-in via /afc:learner enable)
Version Sync (dev)
✓ Version triple match (1.1.0)
✓ Cache in sync
Skill Definitions (dev)
✓ Frontmatter exists (29 files)
✓ Required fields present
✓ Name-filename match
✓ Fork-agent references valid
Agent Definitions (dev)
✓ Frontmatter exists (12 files)
✓ Required fields present
✓ Name-filename match
✓ Expert memory configured (8/8)
✓ Worker maxTurns configured (2/2)
Doc References (dev)
✓ Referenced docs exist
✓ Domain adapters exist (3 files)
─────────────────────────
Results: 26 passed, 2 warnings, 0 failures
2 warnings found. Non-blocking but review recommended.
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 · 127 lines · 13 tokens per session scan A 8fe32ce34070
afc:doctor is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,040 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-31.
Other skills, from other repositories
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
investigate
Systematic root-cause debugging: find the cause before writing any fix.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eight checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
optimize
Analyze and suggest performance improvements for code, queries, or systems.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.