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/Insajin/autopus-adkWrote 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/insajin/autopus-adk/auto-doctor)<a href="https://agentmods.dev/commands/insajin/autopus-adk/auto-doctor"><img src="https://agentmods.dev/badge/commands/insajin/autopus-adk/auto-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/insajin/autopus-adk/auto-doctor"><img src="https://agentmods.dev/badge/commands/insajin/autopus-adk/auto-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.00017 | $0.00099 |
| Opus 5 | $0.00009 | $0.00049 |
| Sonnet 5 | $0.00003 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
auto-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 11d 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.
This is a copy
78% identical to auto-dev — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
$ARGUMENTS
Treat the text above as the full argument payload for /auto-doctor.
Load exact detail skill auto-doctor; this is the same target selected by /auto doctor ....
Preserve --model <provider/model> and --variant <value> when present.
Do not restate or expand the arguments unless needed for execution.
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.
- 11d ago First seen · 12 lines · 17 tokens per session scan A 48419ce567d1
auto-doctor is a command published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 99 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to auto-dev, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
debug-help
Structure debugging requests to efficiently identify and resolve issues.
performance-optimization
Optimize code, queries, or systems for better performance with a structured profiling and analysis approach.
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
investigate
Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…
review-errors
Find one defect: a real failure crosses the changed code and becomes indistinguishable from success to the caller, operator, or user who must react. Not every error needs logging; recovery is correct when the contract permits it and the right owner can still observe the outcome. Read-only: never modify files, commit…
pr-quality-gate-reliability
You are reviewing a pull request for production survivability: how the change behaves when its dependencies misbehave, time out, or fail.