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.
git clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/vs-doctor)<a href="https://agentmods.dev/commands/mtarcure/claude-vibe-squad/vs-doctor"><img src="https://agentmods.dev/badge/commands/mtarcure/claude-vibe-squad/vs-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/commands/mtarcure/claude-vibe-squad/vs-doctor"><img src="https://agentmods.dev/badge/commands/mtarcure/claude-vibe-squad/vs-doctor.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.00000 | $0.00196 |
| Opus 5.5 | $0.00000 | $0.00078 |
| Sonnet 5.5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
vs-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 today.
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
/vs-doctor
Run the Vibe Squad health check + runtime diagnostics (the same fast pre-flight
squad up gates on).
Run:
bash "$(git rev-parse --show-toplevel)"/bin/squad doctor
This is the FAST health check: CLI presence + auth, MCP reachability, vault root,
disk, tmux window composition, dispatch volume, and the notification spine. It is
diagnostic — it verifies and reports, and never mutates board or mailbox state.
It does write its own daily health report under
_state/.../doctor-logs/<date>.md (that report is the check's output, and what
/vs-status reads back). For the costlier checks the fast path defers, run
squad doctor --deep in a terminal.
Use this when the operator says /vs-doctor, "is everything healthy", or asks to run diagnostics.
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.
- today First seen · 21 lines · 0 tokens per session scan A 99dafcd47bed
vs-doctor is a command published in the GitHub repository mtarcure/claude-vibe-squad (178 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 196 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-10-29.
Other commands, from other repositories
afr
Review feature - code review with fixes by a different agent (shortcut for feature-code-review).
scramjet:troubleshoot
Diagnose unexpected command behavior and recommend safe resolution.
fix
Diagnose and fix bugs, errors, and issues in code.
bobby-debug
Root-cause investigation — structured debugging methodology.
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.