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 hackermanishackerman/claude-skills-vault --skill doc-navigatorgit clone --depth 1 https://github.com/hackermanishackerman/claude-skills-vaultWrote 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/hackermanishackerman/claude-skills-vault/doc-navigator)<a href="https://agentmods.dev/skills/hackermanishackerman/claude-skills-vault/doc-navigator"><img src="https://agentmods.dev/badge/skills/hackermanishackerman/claude-skills-vault/doc-navigator/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/hackermanishackerman/claude-skills-vault/doc-navigator"><img src="https://agentmods.dev/badge/skills/hackermanishackerman/claude-skills-vault/doc-navigator.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.00057 | $0.00993 |
| Opus 5 | $0.00028 | $0.00496 |
| Sonnet 5 | $0.00011 | $0.00199 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
doc-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 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.
This is a copy
100% identical to doc-navigator — 244 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Navigator
Navigate codebase documentation efficiently by checking known doc locations first, before resorting to grep/glob searches.
When to Use
- Finding architectural decisions (ADRs)
- Locating feature specs or API docs
- Researching codebase before implementation
- Suggesting documentation structure for new projects
- Alternative to grep/glob for doc discovery
Quick Start
- Check for docs directory at project root
- Scan for common doc file patterns
- If docs exist → map topics to locations
- If no docs → suggest documentation structure (see
references/doc-patterns.md)
Common Documentation Locations
Check these locations in order:
project-root/
├── docs/ # Primary documentation
│ ├── architecture/ # System design, ADRs
│ ├── features/ # Feature specs
│ ├── api/ # API documentation
│ └── guides/ # How-to guides
├── .github/ # GitHub-specific docs
│ └── docs/
├── README.md # Project overview
├── ARCHITECTURE.md # High-level architecture
├── CONTRIBUTING.md # Contribution guidelines
└── doc/ or documentation/ # Alternative doc folders
Topic-to-Location Mapping
| Looking for... | Check first |
|---|---|
| Project overview | README.md |
| Architecture/design | docs/architecture/, ARCHITECTURE.md, docs/adr/ |
| Feature specs | docs/features/, docs/specs/ |
| API reference | docs/api/, api-docs/, OpenAPI/Swagger files |
| Setup/installation | docs/guides/setup.md, INSTALL.md |
| Database schema | docs/database/, docs/schema/, prisma/schema.prisma |
| Data types/models | docs/types/, docs/models/, src/types/, src/models/ |
| Style guide | docs/style-guide.md, docs/conventions.md, .eslintrc, STYLE.md |
| Environment config | docs/config/, .env.example, docs/environment.md |
| Testing strategy | docs/testing/, tests/README.md |
| Deployment | docs/deployment/, docs/infrastructure/ |
| ADRs (decisions) | docs/adr/, docs/decisions/, architecture/decisions/ |
| ADRs (fallback) | CHANGELOG.md, git log, PR descriptions, code comments |
What ships with it
3 files 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 · 123 lines · 57 tokens per session scan A a9282e76d901
doc-navigator is a skill published in the GitHub repository hackermanishackerman/claude-skills-vault (2 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 993 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to doc-navigator, differing in 244 lines, and is treated as a copy.
Other skills, from other repositories
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
council
Full execution protocol for MODE: COUNCIL -- General Council research, parallel member dispatch, disagreement handling, and synthesis.
deep-research
Full execution protocol for MODE: DEEPRESEARCH — orchestrator-worker deep research over external sources: decompose, iterative websearch/webfetch retrieval, parallel sme synthesis, dual-reviewer claim verification, critic challenge of high-stakes claims, and a cited report. Loaded on demand by the architect when the…
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.