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 agentmods add commands/friedbotstudio/baseline/init-project-doctorgit clone --depth 1 https://github.com/friedbotstudio/baselineWhat 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 | $0.00076 | $0.01453 |
| Opus 5 | $0.00038 | $0.00727 |
| Sonnet 5 | $0.00015 | $0.00291 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade A, and why
init-project-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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init-project doctor — baseline drift detector + repairer
User-only command. Run after a create-baseline upgrade cycle, after manually editing workflows.jsonl, or any time the baseline feels out of sync. Different from create-baseline doctor (the npm CLI manifest-drift checker) — this is a project-internal interactive repair tool.
Step 1 — Pre-flight
- Print: "
/init-project doctor— checking baseline integrity. Each detected violation is presented separately; you confirm each fix via AskUserQuestion." - Verify the project is configured:
.claude/project.json → configured == true. If false, halt with: "Run/init-projectfirst; the project is in agnostic mode." - Verify
node≥ 18.17 available; halt with one-line missing-dep message if not.
Step 2 — Check .claude/workflows.jsonl presence
Restore source depends on the tree shape. A baseline development tree carries pristine templates under its own template directory; a consumer install does not — it received these files from the published package. Resolve the source before offering a restore, and never offer a copy from a path the install does not have.
- If
.claude/workflows.jsonlis missing on disk:- AskUserQuestion: "
.claude/workflows.jsonlmissing. Restore it?" - Options:
Restore|Skip|Show diff - On
Restorein a development tree: copy the pristineworkflowstemplate from the repo's template directory. - On
Restorein a consumer install: re-run the baseline installer's merge (or/upgrade-project) to re-materialize the file from the published package. Report the command rather than fabricating the content. - Either way, log to
.claude/state/init/doctor-<timestamp>.log. - On
Skip: note in report; proceed.
- AskUserQuestion: "
Step 3 — Check .claude/schemas/ presence
- If
.claude/schemas/workflow-track.v1.jsonis missing:- AskUserQuestion: "
.claude/schemas/workflow-track.v1.jsonmissing. Restore it?" - Resolve the restore source exactly as Step 2 does — repo template directory in a development tree, installer re-materialization in a consumer install.
- Apply on
Restore(recursive copy).
- AskUserQuestion: "
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.
- 2d ago First seen · 82 lines · 0 tokens per session scan A 026c0494ee11
init-project-doctor is a command published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 76 tokens to every session and 1,453 once invoked, about $0.0004 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.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
track-mentions
Search for new online mentions of the Claude Code Ultimate Guide and update the tracker.
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
init-docs
Fetch official Anthropic Claude Code docs and store as local baseline snapshot.