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/vyuh-labs/dxkit/doctorgit clone --depth 1 https://github.com/vyuh-labs/dxkitWrote 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/vyuh-labs/dxkit/doctor)<a href="https://agentmods.dev/commands/vyuh-labs/dxkit/doctor"><img src="https://agentmods.dev/badge/commands/vyuh-labs/dxkit/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 | $0.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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 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.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vyuh-dxkit doctor
Run as:
vyuh-dxkit <cmd>afternpm install -g @vyuhlabs/dxkit, ornpx @vyuhlabs/dxkit <cmd>for one-shot use. Examples on this page use the short form.
Diagnose missing tools, version mismatches, environment misconfig. The first stop when something doesn't work.
Usage
vyuh-dxkit doctor [path]
What it checks
| Category | Examples |
|---|---|
| Node version | Node ≥ 18 |
| Tool availability | Every Layer 1 + active-pack Layer 2 tool detected |
| Tool versions | Versions are within known-working ranges |
| Project shape | .git exists, .gitignore reasonable, no obvious mis-config |
| PATH issues | Tool present but not on PATH (e.g. ~/.local/bin missing) |
| Tilde expansion | Tools installed under ~/... paths that didn't get expanded |
| Permissions | .dxkit/reports/ writable |
Output
Human-readable diagnostics with actionable next steps:
✓ Node 20.11.1 (✓ ≥ 18 required)
✓ Project structure looks correct
✓ All Layer 1 tools detected
✗ ruff: not found on PATH
Install with: pipx install ruff
Or: vyuh-dxkit tools install
✗ govulncheck: installed at ~/go/bin/govulncheck but not on PATH
Add to PATH: export PATH="$HOME/go/bin:$PATH"
⚠ osv-scanner: 1.6.0 detected, dxkit tested against ≥ 1.7
Upgrade: brew upgrade osv-scanner
Exit code:
0— no issues1— at least one issue blocking analysis
When to run
- After
npm install -g @vyuhlabs/dxkitto verify setup - When a report says "tool X unavailable"
- When you've installed a new tool and want to confirm dxkit sees it
- In CI before running analyzers to fail fast on env misconfig
See also
tools— list + install missing tools
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 · 60 lines · 0 tokens per session scan A 1ceab6b57c1d
doctor is a command published in the GitHub repository vyuh-labs/dxkit (10 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 497 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
brooks-audit
Run a Brooks-Lint architecture audit.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
research
Research a technical or product question.
debugger
You are the Support & Debug persona in the ColdStart workflow. You are a relentless bug hunter who refuses to accept vague issues, half-documented bugs, or silent failures. You operate under these core assumptions: no error is random, no user report is exaggerated, and every failure is traceable to a flaw in logic…