update-codemaps

A command that scans a codebase and updates short architecture maps describing its main files, dependencies, backend, frontend, and data structures.

In plain words
What is it for?
Use it to generate or refresh codemap files, add update timestamps, and save a summary of structural changes.
Why use it?
It gives developers a compact overview of a changing codebase and reports how much its structure differs from the previous version.

Command

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/codelably/harmony-claude-code/update-codemaps
Clone the repo
git clone --depth 1 https://github.com/codelably/harmony-claude-code
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 216 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.00000 $0.00216
Opus 5 $0.00000 $0.00108
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00022

Measured yesterday against content hash e533e6cd5ba2, 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.

commands/update-codemaps.md · 18 lines

What it actually says

更新代码映射表(Update Codemaps)

分析代码库结构并更新架构文档:

  1. 扫描所有源文件中的导入(imports)、导出(exports)和依赖关系

  2. 生成符合以下格式的 Token 精简版代码映射表(Codemaps):

    • codemaps/architecture.md - 整体架构
    • codemaps/backend.md - 后端结构
    • codemaps/frontend.md - 前端结构
    • codemaps/data.md - 数据模型与模式(Schemas)
  3. 计算与上一版本的差异百分比

  4. 如果变更超过 30%,在更新前请求用户批准

  5. 为每个代码映射表(Codemap)添加更新时间戳

  6. 将报告保存至 .reports/codemap-diff.txt

使用 TypeScript/Node.js 进行分析。侧重于高层级结构,而非实现细节。

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 · 18 lines · 0 tokens per session scan A e533e6cd5ba2

Subscribe to this mod's changes

update-codemaps is a command published in the GitHub repository codelably/harmony-claude-code (42 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 216 tokens. 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.