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/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/doctor)<a href="https://agentmods.dev/commands/fjpulidop/specrails-core/doctor"><img src="https://agentmods.dev/badge/commands/fjpulidop/specrails-core/doctor.svg" alt="Measured on agentmods" 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.00389 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
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 7d 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.
What it actually says
Doctor: specrails Health Check
Run the specrails health check to validate that all prerequisites are correctly configured for this repository.
What it checks
| Check | Pass condition |
|---|---|
| Claude Code CLI | claude binary found in PATH |
| Claude API key | claude config list shows a key OR ANTHROPIC_API_KEY env var set |
| Agent files | Generated agent files exist under .claude/agents/ |
| CLAUDE.md | CLAUDE.md present in the repo root |
| Git initialized | .git/ directory present |
| npm | npm binary found in PATH |
How to run
This command uses the Node-native doctor runtime. Run it directly with:
npx specrails-core@latest doctor
If specrails-core is already on your PATH, this works too:
specrails-core doctor
Output
Each check is displayed as ✅ (pass) or ❌ (fail with fix instruction).
On all checks passed:
All 6 checks passed. Run /specrails:implement to get started.
On failure:
❌ API key: not configured
Fix: Run: claude config set api_key <your-key> | Get a key: https://console.anthropic.com/
1 check(s) failed.
Exit codes
0— all checks passed1— one or more checks failed
Log file
Each run appends a timestamped summary to ~/.specrails/doctor.log:
2026-03-20T10:00:00Z checks=6 passed=6 failed=0
The ~/.specrails/ directory is created automatically if it does not exist.
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.
- 7d ago First seen · 63 lines · 0 tokens per session scan A 9ca87dbdbdc3
doctor is a command published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 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-31.
Other commands, from other repositories
cpp-build
Fix C++ build errors, CMake issues, and linker problems incrementally. Invokes the cpp-build-resolver agent for minimal, surgical fixes.
flutter-build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
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.
quick-fix
Run the implement→review subagent loop without the planning phase — for straightforward fixes with a known cause and one obvious approach, regardless of how many files the change spreads across. Skips the spec gate, worktree gate, and finalize ceremony (implementation log, docs, signals) that /subagent-implementation…
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.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.