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/narailabs/doc-wiki/claude-mdgit clone --depth 1 https://github.com/narailabs/doc-wikiWrote 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/narailabs/doc-wiki/claude-md)<a href="https://agentmods.dev/instructions/narailabs/doc-wiki/claude-md"><img src="https://agentmods.dev/badge/instructions/narailabs/doc-wiki/claude-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.04311 | $0.04311 |
| Opus 5 | $0.02155 | $0.02155 |
| Sonnet 5 | $0.00862 | $0.00862 |
| Haiku 4.5 | $0.00431 | $0.00431 |
Grade A, and why
doc-wiki CLAUDE.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 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-wiki
Documentation wiki generator and maintainer. Runs entirely inside Claude Code as skills + agents + TypeScript helper scripts.
Documentation
The public-facing documentation lives under docs/. Start there for installation, usage, and architecture details.
| Audience | Read |
|---|---|
| Brand new — installing | README.md, docs/getting-started.md |
| Operator — using the commands | docs/commands.md, docs/configuration.md, docs/troubleshooting.md |
| Contributor — modifying internals | docs/internals/architecture.md, docs/internals/connectors-api.md, CONTRIBUTING.md |
This file (CLAUDE.md) is the project-memory layer that Claude Code loads automatically; the sections below are an architecture summary for the orchestrator. The full architecture doc with Mermaid diagrams is at docs/internals/architecture.md.
Quickstart
Three slash commands take a new repo from zero to a working wiki:
/doc-wiki:init # scaffold + onboard + (optionally) chain /doc-wiki:atlas
/doc-wiki:ingest <src> # fetch a source, compile, link, diagram, index
/doc-wiki:query <q> # search the wiki, optionally save the answer as a page
/doc-wiki:init Phase 3 (onboarding) walks the user through configuring narai-primitives's ~/.connectors/config.yaml from .connectors/config.example.yaml (in this repo). After that, every /doc-wiki:ingest <jira-url>, /doc-wiki:ingest <github-repo>, etc. routes through gather() to the right connector — no per-service setup needed.
Architecture
- Main skill:
skills/doc-wiki/SKILL.md— orchestrates all/doc-wiki:*commands - Slash-command wrappers:
commands/*.md— 8 thin wrappers so/doc-wiki:init,/doc-wiki:atlas,/doc-wiki:ingest,/doc-wiki:query,/doc-wiki:lint,/doc-wiki:edit,/doc-wiki:unarchive,/doc-wiki:statsappear in Claude Code's slash-command autocomplete and route into the skill - Source-fetch dispatch:
/doc-wiki:ingeststep 7 callsgather()fromnarai-primitives, which plans and spawns the bundled connector CLIs in parallel. The wiki-side Mermaid augmentation runs on the raw envelopes viaagents/lib/mermaid_augment.ts. There is one path: gather → applyMermaid. The legacywiki-<svc>-agentsubagents + their per-service wrappers were decommissioned — their CLI-resolution and Mermaid responsibilities are now wholly owned by the hub andmermaid_augment.ts. - No standalone CLI — all LLM calls go through Claude Code's session
- Runtime: Node 20. All scripts are TypeScript;
npm run buildemits sibling.jsfiles that are invoked withnode.
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 · 217 lines · 4,311 tokens per session scan A bb2930e68fb2
doc-wiki CLAUDE.md is an instructions file published in the GitHub repository narailabs/doc-wiki (13 stars, last pushed 4d ago), licensed Apache-2.0. It adds 4,311 tokens to every session, about $0.0216 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.