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/update-docs/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/update-docs)<a href="https://agentmods.dev/skills/stainless-code/codemap/update-docs"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/update-docs/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/update-docs"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/update-docs.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.00072 | $0.01133 |
| Opus 5.5 | $0.00029 | $0.00453 |
| Sonnet 5.5 | $0.00014 | $0.00227 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
update-docs 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update docs — sync apps/docs with merged PRs
Upstream workflow: npx skills add haydenbleasel/blume --skill blume-update-docs. This local skill encodes it for scheduled agents in this repo.
When to use
- Scheduled — weekly (or similar) run to catch docs drift from merged PRs.
- On demand — after a batch of merged PRs that may have changed public API surfaces, recipes, schema, or Blume config.
Workflow
- Collect merged PRs in the lookback window (default 7 days):
git log --since="7 days ago" --merges --first-parentandgh pr list --state merged --search "merged:>$DATE". Done: every merged PR in the window listed with title, number, and surfaces touched. - Drop feature-flagged work — skip PRs/commits touching flag-gated code; never document unreleased surfaces. Done: flag-gated PRs removed from the list.
- Map changed surfaces to docs pages — trace diffs in
src/cli/,src/application/,src/adapters/,src/db.ts(createTables()/SCHEMA_VERSION),package.jsonexports,blume.config.ts/apps/docs/**,templates/recipes/*.{sql,md},templates/agent-content/**, and TypeDoc-facing JSDoc to the pages that document them (content/reference/api/**generated,content/reference/**hand,content/guides/**,content/recipes/**,content/concepts/**, plus homepage_home/**when behavior framing changed). Regenerate API MDX viabun run docs:apiwhen public exports/JSDoc drifted. Done: every changed public surface mapped to zero or more docs pages. - Edit only drifted facts — signatures, option tables, recipe ids, schema columns, behavior descriptions, entry-point peers. Use
docs-voice; do not rewrite stable prose. Peer framing stays code-index / agent-context tools only — never store/adapter middlewares. Done: every drifted fact updated; no stable prose touched. - Verify —
bun run docs:validate -- --strict && bun run docs:check -- --isolated && bun run docs:build && bun run docs:audit(run fromapps/docs/or via rootdocs:*scripts); fix until green. Do not commit if any fail. Perverify-after-each-step. Done: all four green. - Open or update a PR on branch
docs/sync-<date>with a summary of what drifted and the fixes. Label itdocsso merge deploys/codemapvia FTP (docs-governance/LIFECYCLE.md§ README surfaces). Follow commit/PR conventions; never--no-verify(no-bypass-hooks). Changeset for a docs-only sync ispatch(pre-1.0; schema-breaking is the onlyminortrigger). Done: PR open withdocslabel and drift summary, or step 7 applies. - Clean no-op — if nothing drifted, report the PRs checked and surfaces audited; do not open a PR. Done: report lists every PR checked and every surface audited.
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 · 37 lines · 72 tokens per session scan A 61f68d360acf
update-docs is a skill published in the GitHub repository stainless-code/codemap (8 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 1,133 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.