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 instructions/garagon/nanostack/agents-mdgit clone --depth 1 https://github.com/garagon/nanostackWrote 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/instructions/garagon/nanostack/agents-md)<a href="https://agentmods.dev/instructions/garagon/nanostack/agents-md"><img src="https://agentmods.dev/badge/instructions/garagon/nanostack/agents-md.svg" alt="Measured on agentmods" 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 | $0.00935 | $0.00935 |
| Opus 5 | $0.00467 | $0.00467 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
nanostack AGENTS.md 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 4d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nanostack: Agent Discovery
This file lists every built-in skill shipped by Nanostack for the verified adapters: Claude Code, Cursor, OpenAI Codex, OpenCode, and Gemini CLI. Each skill folder contains a SKILL.md for adapter discovery and an agents/openai.yaml for OpenAI-compatible agents. Adapter capability evidence lives in adapters/<host>.json; treat the JSON as the single source of truth for what a given host actually enforces (hook execution, write guard, phase gate).
Available skills
Default sprint
| Skill | Directory | Description |
|---|---|---|
| think | think/ |
Refines a rough idea before code: questions one at a time, alternatives with trade-offs, design walked in sections. Calibrated per archetype. Saves a structured artifact (value proposition, scope mode, target user, narrowest wedge, key risk, premise validation). |
| nano | plan/ |
Implementation planning. Planned files, plan approval, scope assessment, product standards. |
| review | review/ |
Two-pass code review (structural + adversarial). Scope drift detection against /nano. Conflict precedence with /security. |
| qa | qa/ |
Browser, API, CLI, or debug testing. WTF heuristic. |
| security | security/ |
OWASP Top 10 + STRIDE audit. Cross-references /review for conflicts. |
| ship | ship/ |
Pre-flight, PR creation, CI monitoring, post-deploy verification. Generates the sprint journal on success. |
| compound | compound/ |
Knowledge capture after /ship. Promotes proven solutions across sprints (bug, pattern, decision) with confidence and applied_count. |
Orchestration and safety
| Skill | Directory | Description |
|---|---|---|
| guard | guard/ |
Block and warn rules on Bash + Write/Edit. Phase concurrency, sprint phase gate, and budget gate run inside the same pipeline. Rule counts live in guard/rules.json. |
| conductor | conductor/ |
Multi-agent sprint orchestrator. Parallel sessions via claim/complete protocol with atomic file locking. |
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.
- 4d ago First seen · 50 lines · 935 tokens per session scan A 989b0a3843fc
nanostack AGENTS.md is an instructions file published in the GitHub repository garagon/nanostack (204 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 935 tokens to every session, about $0.0047 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 instructions, from other repositories
superset CLAUDE.md
Claude Code instructions for superset-sh/superset, a project described as: Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.