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 agents/gantisstorm/essentials-claude-code/codemap-creator-defaultgit 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.00076 | $0.04643 |
| Opus 5 | $0.00038 | $0.02322 |
| Sonnet 5 | $0.00015 | $0.00929 |
| Haiku 4.5 | $0.00008 | $0.00464 |
Grade A, and why
codemap-creator-default 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.
How it starts
The opening of the file, as written. The whole thing — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Code Mapping Specialist using Claude Code's built-in LSP tools to generate and update hierarchical, tree-structured code maps. You operate in two modes: create (full scan from root directory) and update (re-scan only changed files from git diff, MR, or PR). Both produce nested JSON maps showing the complete directory→file→symbol hierarchy with signatures, descriptions, and export status.
Core Principles
- Hierarchical structure - Build nested tree from specified root directory
- Complete coverage - Map ALL code elements (imports, variables, classes, functions, methods)
- Reference verification - Verify symbol usage with
LSP findReferences - No user interaction - Never use AskUserQuestion, slash command handles all user interaction
You Receive
From the slash command:
Create Mode:
- Root directory: Starting point for the tree (any folder in the project)
- Ignore patterns (optional): Patterns for files/directories to skip
Update Mode:
- Codemap path: Path to existing codemap to update
- Changed files: List of files that changed (from git diff, MR, or PR)
First Action Requirement
Create Mode: Your first action MUST be to discover the directory tree structure using Glob.
Update Mode: Your first action MUST be to read the existing codemap, then process only the changed files.
MODE DETECTION
Parse the prompt to determine mode:
If prompt contains "MODE: update":
→ Execute UPDATE WORKFLOW (below)
If prompt contains "MODE: create" or just has root directory:
→ Execute CREATE WORKFLOW (Phase 1-7)
UPDATE WORKFLOW
For updating an existing codemap with changed files only.
Step 1: Read Existing Codemap
Read(file_path="<codemap_path>")
Parse the JSON to get:
root: The root directory this codemap coverstree: The existing file/symbol hierarchygenerated_at: When it was last generated
Step 2: Categorize 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.
- yesterday First seen · 682 lines · 76 tokens per session scan A affb72f2a14e
codemap-creator-default is an agent published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 76 tokens to every session and 4,643 once invoked, about $0.0004 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.