Borrowing it
Nothing to install: this file belongs to stainless-code/codemap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stainless-code/codemap/main/.agents/skills/docs-voice/SKILL.mdgit clone --depth 1 https://github.com/stainless-code/codemapWrote 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/stainless-code/codemap/docs-voice)<a href="https://agentmods.dev/skills/stainless-code/codemap/docs-voice"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/docs-voice/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/stainless-code/codemap/docs-voice"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/docs-voice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01726 |
| Opus 5.5 | $0.00026 | $0.00690 |
| Sonnet 5.5 | $0.00013 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
docs-voice 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs voice — Codemap docs (apps/docs, built with Blume)
Keep landing, guides, concepts, recipes, reference, and generated API reading like one voice.
Voice in one line
Senior-dev to senior-dev: concrete, SQL-literate, dry, honest about scope. No hype. The differentiators are radical honesty (say what's planned / diverges / was rejected) and the "when not to use it" anti-pitch — keep both.
Do
- Lead with the pain, then the mechanism. "Agents burn tokens scanning files
to find one symbol…" → then "
codemap query --jsonreturns the row in one SQL round-trip." - Concrete before abstract. Name
codemap query/--recipe/createCodemap/defineConfigbefore the coinage "predicate-as-API" or "structural index." - CLI-first AND programmatic. Show the CLI shape first; pair with the library
shape (
createCodemap,defineConfig, adapters) when the page is API-shaped. The published package entry is the SSOT for generated/reference/api(TypeDoc). - SQL is the API. When a page answers a structural question, show the SQL or
the
--recipe— not a paragraph of prose pretending to be the answer. Recipes are named SQL patterns; cite the recipe id. - Section headers by page type. Marketing = period-terminated benefit sentence ("Query your codebase."); guides = action verb ("Find a symbol with one query"); reference = precise noun; concepts = model noun + consequence.
- Card titles = the outcome; card bodies = the API / SQL.
- One idea per sentence in leads. Short claim first, then expand.
- State experimental / pre-1.0 status once per surface, one wording (see Canonical patterns).
- Sidebar icons: all-or-none per sibling list. Blume does not reserve an
icon column — sparse
sidebar.iconjaggeds labels. Guides, Concepts, Recipes, Reference leaves: none unless every peer has a natural glyph. Sectionmeta.tsicons and tab icons stay. - Peer framing is structural, not brand-vs-brand. When comparing, contrast
axes (query API, semantic layer, extraction depth, CI substrate) — see
docs/why-codemap.md§ Codemap vs alternatives. Do not clone peer design in prose; reach for the underlying spec (plan-pr-inspiration-discipline).
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.
- 1mo ago First seen · 122 lines · 65 tokens per session scan A f0bf1ff19764
docs-voice is a skill published in the GitHub repository stainless-code/codemap (8 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,726 once invoked, about $0.0003 per session on Opus 5.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
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
codestory-grounding
Use when discovering repository structure, tracing relationships, analyzing change impact, or validating CodeStory retrieval or an installed plugin through the CodeStory plugin MCP. Skip only for bounded inspection or editing of named files that does not require those operations.
agentmap
Use for TypeScript/JavaScript codebase navigation — symbol lookup, blast radius, reuse checks, and repo orientation. Prefer agentmap before serial grep when exploring imports, exports, or where a symbol lives. Package is @raymondchins/agentmap (not the unrelated npm package agentmap).
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
sipcode-regress
Check the user's own local Claude Code and Codex logs for regressions after an update (prompt-cache misses, 5-minute cache TTL, uncached context, hourly cache rebuilds, Codex usage limit draining faster per token) and pin each one to the version that introduced it, using the Sipcode CLI. Use when the user asks whether…
analyze-usage
Use when asked to analyze codescout tool usage, check for error patterns, audit tool health, generate a usage report, spot anti-patterns, or clear usage statistics to start fresh.