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/punt-labs/z-spec/doctor-devgit clone --depth 1 https://github.com/punt-labs/z-specWrote 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/punt-labs/z-spec/doctor-dev)<a href="https://agentmods.dev/commands/punt-labs/z-spec/doctor-dev"><img src="https://agentmods.dev/badge/commands/punt-labs/z-spec/doctor-dev.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 | $0.00005 | $0.01021 |
| Opus 5 | $0.00003 | $0.00511 |
| Sonnet 5 | $0.00001 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade B, and why
doctor-dev scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
— no `sudo texhash` step is needed or effective, since `TEXMFHOME` is not How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Z Environment Health Check
Run diagnostic checks on the Z specification toolchain and report results in a status table.
Checks
Run all checks, collecting results before producing output. Run independent checks in parallel where possible.
1. Platform (informational)
uname -s # Darwin or Linux
uname -m # arm64, x86_64, etc.
2. Required toolchain (fuzz, probcli, plugin version)
Call mcp__plugin_z-spec-dev_zspec__doctor. It returns
{version, fuzz, probcli, healthy} — the plugin version string, the
resolved fuzz and probcli binary paths (or null when absent), and
an overall healthy flag for the required pair.
Report fuzz and probcli as presence, not version: installed (<path>) when
the path field is set, not found when it is null. Do not report fuzz or
probcli binary version strings — the tool does not provide them. (Binary
versions return once DoctorReport is widened; that work is beaded.)
fuzznull: suggestRun /z-spec-dev:setup-dev fuzz.probclinull: suggestRun /z-spec-dev:setup-dev probcli.
probcli handles both Z specifications (.tex) and B machines (.mch, .ref, .imp).
3. fuzz.sty (required)
kpsewhich fuzz.sty
If missing: suggest Run /z-spec-dev:setup-dev fuzz. That installs fuzz.sty into
TEXMFHOME and refreshes that tree's filename database itself, unprivileged
— no sudo texhash step is needed or effective, since TEXMFHOME is not
the system tree texhash rebuilds.
4. Tcl/Tk (conditional — macOS only)
Only check on Darwin. Present if EITHER Homebrew has tcl-tk OR wish is on
PATH (catches installs outside Homebrew). The probe always prints one line,
so the status table populates even when brew is absent:
brew list tcl-tk >/dev/null 2>&1 || command -v wish >/dev/null 2>&1 && echo "Tcl/Tk: installed" || echo "Tcl/Tk: not found"
If it prints not found on macOS: suggest brew install tcl-tk.
5. elan (optional — for /z-spec-dev:prove-dev)
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.
- 5d ago First seen · 120 lines · 5 tokens per session scan B f1a4a20c7ca3
doctor-dev is a command published in the GitHub repository punt-labs/z-spec (5 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 1,021 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
meeting-listen
Play back a completed meeting summary as a voiced debate between personas.
meeting-hive
Run an autonomous PR/FAQ review meeting where four personas debate and reach consensus without user intervention.
vote
Assess whether a PR/FAQ should move forward with a structured go/no-go decision.
feedback
Incorporate feedback into PR/FAQ and redraft affected sections.
feedback-to-us
Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback).
badge
Generate a stage-colored badge and embed it in your README.