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 thettwe/nyann --skill doctorgit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/doctor)<a href="https://agentmods.dev/skills/thettwe/nyann/doctor"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/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/thettwe/nyann/doctor"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/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.00152 | $0.01828 |
| Opus 5 | $0.00076 | $0.00914 |
| Sonnet 5 | $0.00030 | $0.00366 |
| Haiku 4.5 | $0.00015 | $0.00183 |
Grade A, and why
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doctor
Read-only audit. Never mutates the filesystem. Wraps
bin/doctor.sh, which internally runs bin/retrofit.sh --report-only.
1. Resolve the profile
doctor.sh requires --profile <name>. The skill's job is to pick the
right one without pestering the user:
- Look for a
.nyann/profileor equivalent profile hint in the repo. - If the repo's CLAUDE.md declares an active profile, use that.
- If neither exists, ask the user which profile to audit against
(
default,nextjs-prototype,python-cli, or any user/team profile they've installed). Don't silently pickdefault— the audit is only meaningful against an intended baseline.
2. Invoke
bin/doctor.sh --target <cwd> --profile <name> [--json] [--scope <csv>]
--profile takes a bare profile name (e.g. python-cli, nextjs-prototype),
not a filesystem path. The script resolves the name to the profile JSON internally.
Pass --json when the user says "machine-readable", "as JSON",
"pipe this", or similar — otherwise emit the human-readable report.
Pass --scope <csv> when the user wants to inspect only a subset of
the audit — e.g. "just check my docs", "are my hooks healthy". Accepts
any of docs, hooks, branching, gitignore, editorconfig,
github, history, all, comma-separated. When narrower than all,
the rendered output gains a Scope: <csv> line and --persist is
auto-disabled (a partial-scope health score would corrupt the trend
series in memory/health.json).
3. Interpret the exit code
| Code | Meaning | What to tell the user |
|---|---|---|
| 0 | clean | "No drift. Hygiene and docs look healthy." |
| 4 | warnings only | "Not failing, but some things have drifted. Here's the list." Offer to remediate via retrofit. |
| 5 | critical | "Missing required files or broken internal links. Run retrofit to fix." |
4. Sections in the report
The output has several blocks. When the user asks "what does each section mean?", explain in terms of the repo, not nyann internals:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 147 lines · 152 tokens per session scan A 96985c1c7929
doctor is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 9d ago), licensed MIT. It adds 152 tokens to every session and 1,828 once invoked, about $0.0008 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
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.