Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-codenpx agentmods add agents/gantisstorm/essentials-claude-code/codemap-creator-defaultWrote 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/agents/gantisstorm/essentials-claude-code/codemap-creator-default)<a href="https://agentmods.dev/agents/gantisstorm/essentials-claude-code/codemap-creator-default"><img src="https://agentmods.dev/badge/agents/gantisstorm/essentials-claude-code/codemap-creator-default/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/gantisstorm/essentials-claude-code/codemap-creator-default"><img src="https://agentmods.dev/badge/agents/gantisstorm/essentials-claude-code/codemap-creator-default.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00076 | $0.04643 |
| Opus 5.5 | $0.00030 | $0.01857 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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 (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 76 tokens to every session and 4,643 once invoked, about $0.0003 per session on Opus 5.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
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.