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/nikzlabs/shipit/docs-navigatornpx skills add nikzlabs/shipit --skill docs-navigatorgit clone --depth 1 https://github.com/nikzlabs/shipitWrote 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/nikzlabs/shipit/docs-navigator)<a href="https://agentmods.dev/skills/nikzlabs/shipit/docs-navigator"><img src="https://agentmods.dev/badge/skills/nikzlabs/shipit/docs-navigator.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.00081 | $0.00963 |
| Opus 5 | $0.00041 | $0.00481 |
| Sonnet 5 | $0.00016 | $0.00193 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
docs-navigator 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Docs Navigator
ShipIt has feature docs in docs/NNN-feature-name/plan.md. Each describes how a feature was designed and implemented. Most tasks don't need these — the architecture skills cover cross-cutting patterns. Load a feature doc only when you need implementation details for a specific feature.
How to use
- Run the index script to get the current list of docs with their status and title:
bash .claude/skills/docs-navigator/index.sh - Find the relevant doc(s) from the output
- Read its
plan.mdfor design details - Check
checklist.mdif it exists — it tracks remaining work
Status key
- done — implemented and shipped
- in-progress — actively being worked on
- planned — designed but not yet started
- paused — designed but not currently scheduled
Filtering
The index script accepts an optional filter argument to narrow results:
# Show only planned/in-progress docs
bash .claude/skills/docs-navigator/index.sh active
# Show only docs matching a keyword
bash .claude/skills/docs-navigator/index.sh git
bash .claude/skills/docs-navigator/index.sh deploy
Writing docs: folder layout
docs/
NNN-feature-name/
requirements.md — What the feature must do, in the human's terms (required for new features)
plan.md — How the feature works, key files, patterns
checklist.md — Remaining work items or tracking notes
mockup.html — Optional UI prototype committed as reference (or mockup.svg / mocks/)
Features are numbered by creation order. Create docs/NNN-new-feature/ for a new one.
docs/NNN-feature/ is this repo's convention, not the docs list's filter. The scan (markdown.ts → findMarkdownFiles) walks the whole workspace and surfaces every .md file — README.md, RELEASING.md, src/server/shipit-docs/*.md, anything nested. The NNN- prefix and the presence of plan.md / checklist.md / an issue: pointer only decide Tracked-vs-Other grouping and newest-first ordering. So treat any markdown you write as user-visible; don't leave scratch notes in .md.
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.
- 4d ago First seen · 77 lines · 81 tokens per session scan A d157592db91e
docs-navigator is a skill published in the GitHub repository nikzlabs/shipit (6 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 963 once invoked, about $0.0004 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
evaluate-presets
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
oma-design
AI design specialist skill with DESIGN.md management, anti-pattern enforcement, optional Stitch MCP integration, and component library guidance. Covers typography, color systems, motion design (motion/react, GSAP, Three.js), responsive-first layouts, and accessibility (WCAG 2.2).
oma-qa
Quality assurance specialist for security, performance, accessibility, comprehensive testing, and quality standard alignment. Use for test, review, security audit, OWASP, coverage, lint work, and ISO/IEC 25010 or ISO/IEC 29119-aligned QA recommendations.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.
external-resource-context
Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design system, API schema, IaC source, secret…
ralph-specum
Use only when the user explicitly invokes $ralph-specum, requests Ralph Specum in Codex, or asks Ralph Specum to handle a named phase or optional prototype.