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 skills add JetXu-LLM/DocMason --skill workspace-doctorgit clone --depth 1 https://github.com/JetXu-LLM/DocMasonWrote 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/skills/jetxu-llm/docmason/workspace-doctor)<a href="https://agentmods.dev/skills/jetxu-llm/docmason/workspace-doctor"><img src="https://agentmods.dev/badge/skills/jetxu-llm/docmason/workspace-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/skills/jetxu-llm/docmason/workspace-doctor"><img src="https://agentmods.dev/badge/skills/jetxu-llm/docmason/workspace-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00838 |
| Opus 5 | $0.00010 | $0.00419 |
| Sonnet 5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
workspace-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 12d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Doctor
Use this skill when the task is to inspect the current workspace and explain what is missing or degraded.
Required Capabilities
- local file access
- shell or command execution
- ability to summarize structured diagnostics
If the agent cannot inspect local files or run commands, stop and explain that the workspace cannot be diagnosed reliably.
Procedure
- Run
docmason doctor --json. - Explain blockers first, then degraded conditions, then optional follow-up.
- If the environment is not ready and
.venvis absent, direct the next action to./scripts/bootstrap-workspace.sh --yes.- treat the launcher as the governed cold-start preflight and bounded liveness gate for bootstrap Python selection, not as an unbounded trust of whatever
python3happens to be first onPATH - on native Codex, the ordinary path should not branch into manual cache probing or manual recovery before that governed launcher settles
- treat the launcher as the governed cold-start preflight and bounded liveness gate for bootstrap Python selection, not as an unbounded trust of whatever
- Otherwise, if the environment is not ready, direct the next action to
docmason prepare --yes.- treat
mixedanddegradedtoolchain states as repair-needed, not ordinary ask-time ready
- treat
- If
doctorreports a control-plane blocker or pending confirmation, surface that blocker before lower-severity degraded conditions.- for pending native Codex host-access upgrade, direct the next action to switching the thread to
Full access - for pending high-intrusion prepare, direct the next action to
docmason prepare --yes - for pending material sync, direct the next action to
docmason sync --yes
- for pending native Codex host-access upgrade, direct the next action to switching the thread to
- If
office-rendereris blocked:- on macOS with Homebrew already present, recommend
brew install --cask libreoffice-stillordocmason prepare --yes - on macOS without Homebrew, recommend
docmason prepare --yesor the official installer fromhttps://www.libreoffice.org/download/download/ - on Linux, recommend the distro package manager or official packages, then re-run
doctor
- on macOS with Homebrew already present, recommend
- If the normal launcher or
preparepath still cannot complete honestly after the governed automatic path has already had enough access, point the deeper fallback todocs/setup/manual-workspace-recovery.md. - Return the diagnosis to the main agent without mutating workspace state.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 59 lines · 21 tokens per session scan A b2f967107128
workspace-doctor is a skill published in the GitHub repository JetXu-LLM/DocMason (135 stars, last pushed 9d ago), licensed Apache-2.0. It adds 21 tokens to every session and 838 once invoked, about $0.0001 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 skills, from other repositories
PostHog Events Debugging
Event inspection, person lookup, data quality checks.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…