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/chankov/agent-fleetWrote 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/chankov/agent-fleet/doctor-agent-fleet)<a href="https://agentmods.dev/commands/chankov/agent-fleet/doctor-agent-fleet"><img src="https://agentmods.dev/badge/commands/chankov/agent-fleet/doctor-agent-fleet.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.1 | $0.00024 | $0.00651 |
| Opus 5 | $0.00012 | $0.00326 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
doctor-agent-fleet 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 6d 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
Invoke the Doctor scan from the agent-fleet:guided-workspace-setup skill — Step 5 (the preflight scan) — without running the rest of the install flow. Use this when the user wants the repair pass on its own; the full /setup-agent-fleet flow runs the same scan automatically as soon as it detects prior install state.
Walk every install-target directory the chosen coding agent uses (agents/, .claude/agents/, .opencode/agent/ (+ legacy .opencode/agents/), .pi/agents/, .claude/skills/, .opencode/skills/, .pi/skills/, .agents/skills, .claude/commands/, .opencode/commands/, .pi/prompts/, .claude/references/, .claude/hooks/). For each broken symlink, resolve where it pointed, look for a canonical replacement in the source agents/ and skills/ trees, and offer to repair or delete (persona links under .claude/agents/ and .opencode/agent(s)/ are repaired by regenerating a transformed copy via transform-persona, not by re-symlinking the raw source). Common stale names from the pre-merge persona layout: reviewer → code-reviewer, red-team → security-auditor.
Also flag and offer to rewrite any remaining YAML configs (teams.yaml, peers.yaml, etc.) that still reference removed persona names.
Also flag malformed peer entries in .pi/agents/peers.yaml: field lines (persona:, model:, ...) that sit under a team heading before any - name: ... list item. The team-up launcher's minimal parser silently drops such lines, so the peer never spawns and nothing errors — the usual cause is a - name: line lost in an edit. These findings are advisory only: report them with the missing - name: <peer> suggestion, never rewrite the file.
Also validate .ai/agent-fleet-overrides.md when it exists, against the schema in docs/agent-fleet-setup.md: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed agent-hub keys, missing rules: folders and docs: entry points, and ## env required: names that are neither set nor declared in the root .env. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
Present findings as a # | Path | Issue | Suggested fix table and ask the user to pick which fixes to apply.
Never overwrite a regular file — only act on symlinks whose target is missing. Report repaired, deleted, and skipped counts, and append a ## doctor-runs line to .ai/agent-fleet-setup.md with the date, agent, phase (standalone), and counts.
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.
- 6d ago First seen · 18 lines · 24 tokens per session scan A 226ad3eea486
doctor-agent-fleet is a command published in the GitHub repository chankov/agent-fleet (14 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 651 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-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.