A health-check command for a nanostack installation, checking dependencies, permissions, telemetry settings, older-version detection, and connectivity.

Use it to diagnose nanostack setup problems, produce machine-readable results with JSON, work offline, or repair supported permission issues.

It shows which part of the local installation is broken or needs attention, while separating automatic repairs from issues requiring human judgment.

nano-doctor — Skill for Claude Code by garagon

Install

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.

Any agent

npx skills add garagon/nanostack --skill doctor

Clone the repo

git clone --depth 1 https://github.com/garagon/nanostack

Made for: Claude Code.

Or install nanostack, the plugin that ships this one along with the rest of its 18 skills, 1 command.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/garagon/nanostack/doctor/github.svg)](https://agentmods.dev/skills/garagon/nanostack/doctor)

Your own site

<a href="https://agentmods.dev/skills/garagon/nanostack/doctor"><img src="https://agentmods.dev/badge/skills/garagon/nanostack/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/garagon/nanostack/doctor"><img src="https://agentmods.dev/badge/skills/garagon/nanostack/doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,575 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00046	$0.01575
Opus 5	$0.00023	$0.00788
Sonnet 5	$0.00009	$0.00315
Haiku 4.5	$0.00005	$0.00158

Measured 9d ago against content hash 88904dee9a62, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

nano-doctor scanned grade B with 1 finding 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 9d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- `--fix` — repair mechanical issues. Currently covers: `chmod 700` on `~/.nanostack/`, `chmod +x` on the sender, and adding the missing PreToolUse hooks for Bash and Write/Edit/MultiEdit to the local `.claude/settings.j

doctor/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/nano-doctor — Install Health Check

You diagnose the local nanostack install. Ten checks across dependencies, install integrity, the user-scoped home directory, telemetry config, the pre-V5 detection path, and Worker reachability. Output names the category, the check, and a one-line detail. No decorative prose.

This is a diagnostic skill, not a fix-everything skill. Mechanical issues (file permissions, missing chmod +x) repair with --fix. Anything that needs human judgment stays as a warning or failure.

Telemetry preamble

Defensive telemetry init. No-op if telemetry is disabled via NANOSTACK_NO_TELEMETRY=1, ~/.nanostack/.telemetry-disabled, or if the helpers are removed.

_P="$HOME/.claude/skills/nanostack/bin/lib/skill-preamble.sh"
[ -f "$_P" ] && . "$_P" nano-doctor
unset _P

Process

Run the health check script, then summarize what the user actually needs to do:

~/.claude/skills/nanostack/bin/nano-doctor.sh

Optional flags:

--json — machine-readable output. Use when invoked by another tool or when piping to jq. The envelope includes fix_available (boolean), fix_command (the suggested command or null), and session_profile ("guided", "professional", or null when no session exists in the current project). These three fields let calling skills decide whether to surface a one-line repair prompt or a full warning report.
--offline — skip Worker reachability. Use in air-gapped environments or during CI.
--fix — repair mechanical issues. Currently covers: chmod 700 on ~/.nanostack/, chmod +x on the sender, and adding the missing PreToolUse hooks for Bash and Write/Edit/MultiEdit to the local .claude/settings.json. Always backs up the file first as .claude/settings.json.YYYYMMDD-HHMMSS.bak. Never touches your existing permission entries; only adds hooks alongside them.

Interpreting the output

The script prints one line per check, grouped by category. Status values:

ok — passed, nothing to do.
warn — minor issue. Telemetry may report unknown, permissions may be too open, Worker may be unreachable. None of these block /think, /nano, etc.
FAIL — critical issue. A missing dependency or missing skill file. Usage is impaired.

Read the full file on GitHub · 118 lines

Changes

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.

9d ago First seen · 118 lines · 46 tokens per session scan B 88904dee9a62

Subscribe to this mod's changes

nano-doctor is a skill published in the GitHub repository garagon/nanostack (204 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,575 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Debugging ai-agents ai-coding codex developer-tools

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

issue-root-resolution

Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.

Gentleman-Programming/gentle-ai · 45 tokens

rdd-defect-workflow

Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.

Gentleman-Programming/gentle-ai · 41 tokens

memstack-development-performance-audit

Use this skill when the user says 'performance audit', 'why is it slow', 'optimize performance', 'page speed', 'Core Web Vitals', 'lighthouse', 'load time', or needs to diagnose and fix frontend or backend performance issues. Do NOT use for code reviews or security audits.

cwinvestments/memstack · 69 tokens

ijfw-debug

Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug.

FerroxLabs/ijfw · 31 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

nano-doctor