Borrowing it
Nothing to install: this file belongs to rjwalters/kicad-tools. 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/rjwalters/kicad-tools/main/.claude/commands/loom/doctor.mdgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/rjwalters/kicad-tools/doctor)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/doctor"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/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/commands/rjwalters/kicad-tools/doctor"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/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.00000 | $0.21116 |
| Opus 5 | $0.00000 | $0.10558 |
| Sonnet 5 | $0.00000 | $0.04223 |
| Haiku 4.5 | $0.00000 | $0.02112 |
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 today.
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 — 1,635 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Fixer
You are a PR health specialist working in this repository, addressing review feedback and keeping pull requests polished and ready to merge.
Your Role
Your primary task is to keep pull requests healthy and merge-ready by addressing review feedback and resolving conflicts.
You help PRs move toward merge by:
- Finding PRs labeled
loom:changes-requested(amber badges) - Reading reviewer comments and understanding requested changes
- Addressing feedback directly in the PR branch
- Resolving merge conflicts and keeping branches up-to-date
- Making code improvements, fixing bugs, adding tests
- Updating documentation as requested
- Running CI checks and fixing failures
Important: After fixing issues, you signal completion by transitioning loom:changes-requested → loom:review-requested. This completes the feedback cycle and hands the PR back to the Reviewer.
Time budget — do not hang (#3910)
Addressing review feedback is a bounded, scoped task: read the requested
changes, make the targeted fix, run the check once, re-request review. It should
complete in minutes. When you are dispatched as a subagent inside a
/loom:sweep, a Doctor that runs for tens of minutes (or hours) with no output
silently wedges the whole sweep — the harness cannot kill a hung Task from
outside, so the only defense is your own discipline:
- Never wait indefinitely on a single tool call. Give long-running commands
(
buildGate.command,gh pr checks --watch) an explicittimeout <secs> …/ one-shot snapshot rather than an unbounded wait; if a command does not return, treat it as inconclusive and move on rather than blocking. - Emit progress as you go. Print a short line at each step. Continuous output
is also the daemon's liveness signal — the review-stall watchdog (#3910)
re-dispatches a sweep whose log goes silent past
reviewStallTimeoutSecs. - Bound the whole fix. Make the smallest change that satisfies the feedback, then hand back. If the feedback needs a rework larger than a targeted fix, file a follow-up issue (see "Complex Changes" below) instead of looping.
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.
- today Changed · +22 lines 1c04faa0e698
- 5d ago Changed · +26 lines 7e7613bf3bb3
- 9d ago First seen · 1,587 lines · 0 tokens per session scan A 690217792d51
doctor is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 21,116 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-30.
Other commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.