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/gantisstorm/essentials-claude-code/codemap-creatorgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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.00019 | $0.01536 |
| Opus 5 | $0.00010 | $0.00768 |
| Sonnet 5 | $0.00004 | $0.00307 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
codemap-creator 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 2d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Map Creator
Generate or update a hierarchical code map using Claude Code's built-in LSP tools. Maps functions, classes, variables, and imports in a nested tree structure.
Modes
Create Mode (default)
Generate a new codemap from scratch:
/codemap-creator src/
/codemap-creator . --ignore "node_modules,dist"
Update Mode
Update an existing codemap with only changed files:
/codemap-creator --update .claude/maps/code-map-src-a3f9e.json --diff
/codemap-creator --update .claude/maps/code-map-src-a3f9e.json --mr 123
/codemap-creator --update .claude/maps/code-map-src-a3f9e.json --pr 456
Arguments
Create Mode
-
Root directory (required): Starting point for the tree
/codemap-creator src/→ maps fromsrc/as root/codemap-creator backend/services→ maps fromservices/as root/codemap-creator .→ maps entire project as root
-
Ignore patterns (optional): Skip files/directories
/codemap-creator src/ --ignore "*.test.ts,node_modules"
Update Mode
- --update (required): Path to existing codemap to update
- --diff (optional): Use
git diffto find changed files (uncommitted + staged) - --mr (optional): Use GitLab MR to find changed files (via
glab) - --pr (optional): Use GitHub PR to find changed files (via
gh)
If no diff source specified with --update, defaults to --diff.
Hierarchical Output
The codemap shows a nested tree structure from your chosen root:
root_dir/
├── subdir1/
│ ├── file1.ts
│ │ └── symbols: [class UserService, function getUser...]
│ └── nested/
│ └── file2.ts
│ └── symbols: [interface Config...]
├── subdir2/
│ └── file3.ts
│ └── symbols: [function helper...]
└── index.ts
└── symbols: [export *, function main...]
Instructions
Step 1: Parse Input and Detect Mode
Parse $ARGUMENTS to determine mode:
Update Mode (if --update present):
- Extract codemap path after
--update - Detect diff source:
--diff→ usegit diff --name-only+git diff --staged --name-only--mr <id>→ useglab mr diff <id> --name-only--pr <id>→ usegh pr diff <id> --name-only- Default to
--diffif no source specified
- Get list of changed files
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.
- 2d ago First seen · 196 lines · 19 tokens per session scan A 401320ecdb2b
codemap-creator is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 19 tokens to every session and 1,536 once invoked, about $0.0001 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.
Other commands, from other repositories
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
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.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.