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/jansenanalytics/claudex/codebase-navigatornpx skills add JansenAnalytics/claudex --skill codebase-navigatorgit clone --depth 1 https://github.com/JansenAnalytics/claudexWhat 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.00030 | $0.00483 |
| Opus 5 | $0.00015 | $0.00242 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
codebase-navigator 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.
What it actually says
codebase-navigator
Rapidly understand any codebase: identify entry points, map architecture, find key patterns, summarize modules, trace data flow.
When to Use
- Onboarding to a new project
- Understanding unfamiliar code
- Finding where functionality lives
- Mapping dependencies between modules
- Creating architectural overviews
Scripts
codebase-scan.sh
Quick codebase overview — detects languages, frameworks, entry points, file counts.
bash scripts/codebase-scan.sh /path/to/project
bash scripts/codebase-scan.sh .
Output: Markdown summary with languages, frameworks, entry points, directory structure, LOC counts.
module-map.py
Build a module/import dependency map.
python3 scripts/module-map.py --dir src/
python3 scripts/module-map.py --dir src/ --format mermaid
python3 scripts/module-map.py --dir lib/ --format json
Arguments:
--dir <path>— Directory to scan (default:.)--format tree|mermaid|json— Output format (default: tree)
Identifies: core modules (most imported), leaf modules, circular dependencies.
trace-flow.sh
Trace a function/symbol through the codebase.
bash scripts/trace-flow.sh --symbol "handlePayment" --dir src/
bash scripts/trace-flow.sh --symbol "UserService" --depth 3
Arguments:
--symbol <name>— Function/class/string to trace (required)--dir <path>— Directory to search (default:.)--depth <n>— Call chain depth (default: 2)
Uses rg (ripgrep) for fast searching.
References
codebase-patterns.md— Common project structures and how to identify them
Requirements
rg(ripgrep) — For fast code searchingpython3— For module-map.py
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 · 76 lines · 30 tokens per session scan A a51cc63a9577
codebase-navigator is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 483 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-31.
Other skills, from other repositories
code-intelligence
Use this skill when the user needs semantic code navigation backed by a Language Server: jump to definitions or implementations, find references, inspect hover/type information, list document or workspace symbols, or trace incoming and outgoing calls. For such requests you MUST load this skill first to unlock the…
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
Developmental Gene Panel Design Workflow
Panel design for DEVELOPING / dynamic systems (embryonic organs, differentiation, regeneration). The target experiment is usually a LATE / terminal stage, but the biology is a trajectory: terminal cell types are end-products of earlier lineage programs. A panel built from the target stage alone resolves terminal…
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
cymbal
Tree-sitter indexed code navigator. Use the cymbal CLI — not Read, Grep, Glob, or Bash — for finding where symbols are defined, tracing callers and callees, locating interface implementations, understanding the impact of a change, and mapping imports across an existing codebase. Returns precise, token-efficient…