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 skills/jordancoin/codemap/config-setupnpx skills add JordanCoin/codemap --skill config-setupgit clone --depth 1 https://github.com/JordanCoin/codemapWhat 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.00044 | $0.00628 |
| Opus 5 | $0.00022 | $0.00314 |
| Sonnet 5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
config-setup 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codemap Config Setup
Goal
Write or improve .codemap/config.json so future Codemap calls stay focused on the code that matters for this repo.
Use this when
.codemap/config.jsonis missing- The existing config looks like a bare bootstrap instead of a real project policy
- Codemap output is dominated by assets, fixtures, generated files, vendor trees, PDFs, screenshots, models, or training data
- The project stack is obvious, but Codemap is not prioritizing the right parts of the repo
Workflow
-
Inspect the repo quickly before writing config
- Run
codemap . - If needed, run
codemap --deps . - Note the stack markers (
Cargo.toml,Package.swift,*.xcodeproj,go.mod,package.json,pyproject.toml, etc.) - Identify large non-code directories and noisy extensions
- Run
-
Decide whether config is missing, boilerplate, or tuned
- Missing: no
.codemap/config.json - Boilerplate: only generic
onlyvalues, no real shaping, no excludes despite obvious noise - Tuned: contains intentional project-specific includes/excludes, depth, or routing hints
- Missing: no
-
Write a conservative code-first config
- Keep primary source-language
onlyvalues when they help - Add
excludeentries for obvious non-code noise - Set a moderate
depthwhen the repo is broad - Avoid overfitting or excluding real source directories
- Keep primary source-language
-
Prefer stack-aware defaults
- Rust: focus
src,tests,benches,examples; de-prioritize corpora, sample PDFs, training data, large generated artifacts - iOS/Swift: focus app/framework source, tests, package/project manifests; de-prioritize
.xcassets, screenshots, snapshots, vendor/build outputs - TS/JS: focus
src,apps,packages,tests; de-prioritizedist,coverage, Storybook assets, large fixture payloads - Python: focus package roots, tests, tool config; de-prioritize notebooks, data dumps, models, fixtures when they overwhelm code
- Go: focus packages, cmd, internal, tests; de-prioritize generated assets, sample data, vendor-like noise
- Rust: focus
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 · 53 lines · 44 tokens per session scan A 5c63e115f6ee
config-setup is a skill published in the GitHub repository JordanCoin/codemap (685 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 628 once invoked, about $0.0002 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 skills, from other repositories
[object Object]
Skill "[object Object]" from microsoft/apm, covering what this package does, getting started, available primitives and included workflows.
using-ao
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, spawning workers, or managing AO sessions in an AO workspace.
apm-usage
Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any apm CLI command.
stop-that-shit
Keep coding agents focused on requested and necessary work. Use for bounded changes, review-only tasks, scope creep, speculative hardening, unnecessary hashing or dependencies, repeated audit loops, or when the user invokes Stop That Shit.
toolset-design
Design and validate new MCP toolsets, tools, and tool changes. Use when planning a new toolset, adding tools to an existing toolset, reviewing a toolset PR, or deciding whether a new tool is warranted. Covers the full lifecycle: eval-first validation, tool design methodology, consolidation patterns, and review…
sessions
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior…