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 Insajin/autopus-adk --skill auto-doctorgit 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/skills/insajin/autopus-adk/auto-doctor)<a href="https://agentmods.dev/skills/insajin/autopus-adk/auto-doctor"><img src="https://agentmods.dev/badge/skills/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/skills/insajin/autopus-adk/auto-doctor"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/auto-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.00144 |
| Opus 5 | $0.00010 | $0.00072 |
| Sonnet 5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00014 |
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.
What it actually says
auto-doctor
OMP Invocation
/auto doctor .../auto-doctor ...- Load detail skill
auto-doctorfor either entrypoint.
실행 계약
상태 진단 — 하네스 설치 상태와 플랫폼 wiring을 점검합니다
- 대상 디렉터리와 전달된 인자를 확인합니다.
- Bash tool로
auto doctor를 실행해 harness 설치와 platform wiring을 값으로 진단합니다. - finding별 expected/got과 repair action을 보고합니다.
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 · 22 lines · 21 tokens per session scan A bf628a0715e3
auto-doctor is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 144 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
preflight
Plan-vs-codebase validation — verifies API contracts, type names, field accuracy, dependencies, and paths before implementation begins.
error-handling
Error handling patterns for Python and TypeScript applications. Use when designing error hierarchies, implementing retry logic, building error boundaries, or establishing logging strategies. Covers custom exceptions, result types, circuit breakers, and user-facing error messages.
db-testing
Test, debug, and validate database connectivity and queries. Use when diagnosing connection errors, testing configurations, or validating queries before deployment.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
atmos-diagnostics
Atmos diagnostics: machine-readable JSONL event streams, diagnostics.enabled/file/includeoutput, subprocess start/end/output events, masking, and debugging Atmos execution.