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 agentmods add skills/garagon/nanostack/helpnpx skills add garagon/nanostack --skill helpgit clone --depth 1 https://github.com/garagon/nanostackWhat 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 | $0.00034 | $0.00746 |
| Opus 5 | $0.00017 | $0.00373 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
nano-help 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 3d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nano-help — Quick Reference
Show the user a concise overview of nanostack. No walls of text. Organized by what they want to do.
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-help
unset _P
Response
Print this directly:
nanostack
Make your AI agent think first.
What do you want to do?
Start a brand new project → /think (or /think --autopilot)
Add to a project that exists → /feature <what to add>
Already wrote code, check it → /review (then /security, /qa)
Ready to save / publish → /ship
First time using nanostack → /nano-run
Not sure where to start → /think (it helps you decide)
Reference — every command:
Getting started:
/nano-run First-time setup. Configures your project conversationally.
/nano-help You are here.
The sprint:
/think Challenge the scope before building.
/nano Plan the implementation. Files, steps, risks.
build You or the agent writes the code.
/review Two-pass code review. Scope drift detection.
/security OWASP Top 10 + STRIDE audit. Graded A-F.
/qa Test it. Browser, API, CLI, or debug.
/ship Create PR, verify CI, generate sprint journal.
Shortcuts:
/think --autopilot Full sprint. Think, plan, build, review, audit, test, ship.
/feature <description> Add a feature to an existing project with full sprint.
After shipping:
/compound Save what you learned. Future sprints find it automatically.
Safety:
/guard Block dangerous commands. /freeze locks edits to a scope.
Team:
/conductor Parallel sprints across multiple agents or terminals.
Modes (for /review, /security, /qa):
--quick Small changes. Only the obvious.
--standard Default. Normal work.
--thorough Auth, payments, infra. Flag everything.
Update:
/nano-update Pull latest version.
/nano-doctor Diagnose install health (deps, perms, telemetry).
github.com/garagon/nanostack
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.
- 3d ago First seen · 94 lines · 34 tokens per session scan A 5d9683c3cef1
nano-help is a skill published in the GitHub repository garagon/nanostack (204 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 746 once invoked, about $0.0002 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.