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 shortcuts/radin --skill radin-doctorgit clone --depth 1 https://github.com/shortcuts/radinWrote 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/shortcuts/radin/radin-doctor)<a href="https://agentmods.dev/skills/shortcuts/radin/radin-doctor"><img src="https://agentmods.dev/badge/skills/shortcuts/radin/radin-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/shortcuts/radin/radin-doctor"><img src="https://agentmods.dev/badge/skills/shortcuts/radin/radin-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.00062 | $0.00287 |
| Opus 5 | $0.00031 | $0.00143 |
| Sonnet 5 | $0.00012 | $0.00057 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
radin-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 yesterday.
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
Doctor
A read-only health check for radin's own install under ~/.claude. It
confirms that every skill and lib file install.sh copies is present,
checks that radin's own lib shell scripts have valid syntax, and reports
which optional companion tools (rtk, code-review-graph, caveman, ponytail)
are currently reachable. It never mutates anything, which mirrors
install.sh's own "advisory only" stance on companion tools.
Step 1: Run it
RADIN_CLI doctor
Step 2: Report it
Print the full output to the user as-is. It already lists every checked item with its status.
A non-zero exit means one or more expected files are missing or have invalid
syntax. Tell the user to re-run install.sh (or radin-update) to fix it. A
missing companion tool is advisory only, never a failure, so it does not need
that remediation.
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.
- yesterday Changed c9e65e195d83
- 3d ago Changed · +9 lines 2c4aa453b12f
- 12d ago First seen · 24 lines · 62 tokens per session scan A bdd7ff0fc3c3
radin-doctor is a skill published in the GitHub repository shortcuts/radin (5 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 287 once invoked, about $0.0003 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 skills, from other repositories
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
breaking-changes
Use when checking whether a Claude Code update breaks our plugin ecosystem — hooks, agent frontmatter, manifest schema, or skill format.
systematic-debugging
Guides root cause investigation before proposing fixes. Use when debugging, diagnosing failures, investigating test errors, or tracing unexpected behaviour.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.