update-codemaps

A command that scans a project and creates markdown maps of its main parts, such as the user interface, server code, database, integrations, and background jobs. The maps also include the repository structure.

In plain words
What is it for?
Use it to create or refresh architecture documentation under docs/CODEMAPS, optionally starting from a chosen source directory, then review whether the project was classified correctly.
Why use it?
It gives developers a quick overview of an unfamiliar codebase and makes important folders and relationships easier to find.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/fmflurry/settings-opencode/update-codemaps
Clone the repo
git clone --depth 1 https://github.com/fmflurry/settings-opencode

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 188 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.00188
Opus 5 $0.00005 $0.00094
Sonnet 5 $0.00002 $0.00038
Haiku 4.5 $0.00001 $0.00019

Measured yesterday against content hash 08744a766866, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-codemaps 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 yesterday.

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.

.claude/commands/update-codemaps.md · 26 lines

What it actually says

Run the codemap generator script to scan the current working directory and generate documentation under docs/CODEMAPS/.

npx tsx ~/.config/opencode/scripts/codemaps/generate.ts

Output files:

  • INDEX.md — Full overview with repository structure
  • frontend.md — UI components, pages, hooks
  • backend.md — API routes, controllers, middleware
  • database.md — Models, schemas, migrations
  • integrations.md — External services & adapters
  • workers.md — Background jobs, queues, cron tasks

You can optionally pass a source directory argument:

npx tsx ~/.config/opencode/scripts/codemaps/generate.ts ./src

After generation, review the output and suggest improvements if the classification missed important project-specific directories.

Changes

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.

  1. yesterday First seen · 26 lines · 9 tokens per session scan A 08744a766866

Subscribe to this mod's changes

update-codemaps is a command published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 9 tokens to every session and 188 once invoked, about $0.0000 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.