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 commands/loulanyue/awesome-claude-notes/update-codemapsgit clone --depth 1 https://github.com/loulanyue/awesome-claude-notesWrote 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/commands/loulanyue/awesome-claude-notes/update-codemaps)<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/update-codemaps"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/update-codemaps.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.00008 | $0.00355 |
| Opus 5 | $0.00004 | $0.00178 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 5d 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.
This is a copy
100% identical to update-codemaps — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Update Codemaps Command
Update codemaps to reflect current codebase structure: $ARGUMENTS
Your Task
Generate or update codemaps in docs/CODEMAPS/ directory:
- Analyze codebase structure
- Generate component maps
- Document relationships
- Update navigation guides
Codemap Types
Architecture Map
docs/CODEMAPS/ARCHITECTURE.md
- High-level system overview
- Component relationships
- Data flow diagrams
Module Map
docs/CODEMAPS/MODULES.md
- Module descriptions
- Public APIs
- Dependencies
File Map
docs/CODEMAPS/FILES.md
- Directory structure
- File purposes
- Key files
Codemap Format
[Module Name]
Purpose: [Brief description]
Location: src/[path]/
Key Files:
file1.ts- [purpose]file2.ts- [purpose]
Dependencies:
- [Module A]
- [Module B]
Exports:
functionName()- [description]ClassName- [description]
Usage Example:
import { functionName } from '@/module'
Generation Process
- Scan directory structure
- Parse imports/exports
- Build dependency graph
- Generate markdown maps
- Validate links
TIP: Keep codemaps updated when adding new modules or significant refactoring.
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.
- 5d ago First seen · 82 lines · 8 tokens per session scan A 197cef27eb72
update-codemaps is a command published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 355 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to update-codemaps, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
catchup
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/catchup/SKILL.md.
security
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/security/SKILL.md.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.