Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/arrrrny/zuraffanpx agentmods add commands/arrrrny/zuraffa/speckit.md-doctor.reportWrote 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/arrrrny/zuraffa/speckit.md-doctor.report)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.md-doctor.report"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.md-doctor.report/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/arrrrny/zuraffa/speckit.md-doctor.report"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.md-doctor.report.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.00034 | $0.00480 |
| Opus 5.5 | $0.00014 | $0.00192 |
| Sonnet 5.5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
speckit.md-doctor.report 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 1mo 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
MD Doctor — Report
Show the project's current documentation health from MD Doctor's recorded facts. This is read-only: it aggregates state and prints; it never grades or edits.
User Input
$ARGUMENTS
Recognized modifiers:
--run <run-id>: render a specific past report from.specify/md-doctor/reports/<run-id>.mdinstead of the latest.--json: print the aggregated summary as JSON.
With no input, show the latest health summary.
Workflow
Phase 1: Aggregate
bash .specify/extensions/md-doctor/scripts/bash/md-doctor.sh report
(Dev fallback: bash <extension-root>/md-doctor/scripts/bash/md-doctor.sh report.)
This reads .specify/md-doctor/state/facts.json and prints the health summary:
average truthfulness, counts of truthful/stale/false/obsolete, and the
update/delete/create action queue. Add --json for machine form.
Phase 2: Present
If a specific --run was requested, cat that report file and present it.
Otherwise present, in order:
- Headline — average truthfulness /100 and the verdict breakdown.
- Danger first — every
falseandobsoletefile, with its rationale. These are the docs a new agent would wrongly believe. - Action queue —
update, thendelete, thencreate, each as a path list. - Healthy — count of
truthfulfiles (so the user sees the good news too).
If no facts.json exists yet, tell the user to run /speckit.md-doctor.scan first;
do not invent numbers.
Report back
Print the summary and the action queue, and point to
.specify/md-doctor/reports/ for the full latest report. Keep it short — the goal is
a one-glance health check.
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.
- 1mo ago First seen · 58 lines · 34 tokens per session scan A 05a6621c410a
speckit.md-doctor.report is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 480 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.