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/conradkoh/raggrep/codemapgit clone --depth 1 https://github.com/conradkoh/raggrepWhat 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.00000 | $0.03098 |
| Opus 5 | $0.00000 | $0.01549 |
| Sonnet 5 | $0.00000 | $0.00620 |
| Haiku 4.5 | $0.00000 | $0.00310 |
Grade A, and why
codemap 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codemap Meta Rules
Definition
A codemap is an index that shows a map to all relevant files for a given feature. It serves as the single source of truth for understanding how a feature is implemented across the codebase.
A projectmap is a high-level architectural overview that documents the entire project's structure, technology stack, and organizational patterns. Unlike codemaps which focus on specific features, a projectmap provides the foundational context for understanding the overall system architecture.
File Requirements
Codemaps
- Location: All codemaps MUST be stored in
$projectroot/codemaps/folder - Naming: Filename MUST follow pattern
$featurename.codemap.md - Format: MUST be markdown format with structured sections
- Template: MUST follow structure defined in
codemaps/templates/template.codemap.md
Projectmap
- Location: MUST be stored as
$projectroot/codemaps/projectmap.md - Purpose: Provides architectural overview and project structure documentation
- Format: MUST be markdown format with structured sections
- Template: MUST follow structure defined in
codemaps/templates/template.projectmap.md - Scope: MUST cover entire project architecture, not individual features
- Maintenance: MUST be updated when project structure or tech stack changes
File Locations
- Codemap Template:
codemaps/templates/template.codemap.md- Use this template when creating new codemaps - Projectmap Template:
codemaps/templates/template.projectmap.md- Use this template when creating new projectmaps - Projectmap:
codemaps/projectmap.md- High-level project architecture and structure overview - Existing Codemaps:
codemaps/directory - Review existing codemaps for reference and patterns
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 · 339 lines · 0 tokens per session scan A d0732d7b1943
codemap is a command published in the GitHub repository conradkoh/raggrep (22 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,098 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.