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/nickcrew/claude-cortex/codanna-codebase-intelligencenpx skills add NickCrew/Claude-Cortex --skill codanna-codebase-intelligencegit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/skills/nickcrew/claude-cortex/codanna-codebase-intelligence)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/codanna-codebase-intelligence"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/codanna-codebase-intelligence.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.01040 |
| Opus 5 | $0.00014 | $0.00520 |
| Sonnet 5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
codanna-codebase-intelligence 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 today.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codanna Codebase Intelligence
Codanna indexes your codebase and provides semantic search, call graphs, and dependency analysis via MCP tools. Use codanna before grep/find - it understands code structure, not just text patterns.
When to Use
- Finding code: "Where do we handle authentication?" →
semantic_search_docs - Understanding dependencies: "What calls this function?" →
find_callers - Impact analysis: "What breaks if I change this?" →
analyze_impact - Exploring symbols: "Show me the Parser struct" →
find_symbol
Core Tools
Discovery
# Natural language search - finds code by intent, not keywords
semantic_search_docs query:"error handling patterns" limit:5
# Search symbols by name/pattern
search_symbols query:"parse" kind:"function"
# Get full details on a specific symbol
find_symbol name:"process_file"
Relationships
# Who calls this function? (upstream)
find_callers symbol:"validate_input"
# What does this function call? (downstream)
get_calls symbol:"process_request"
# Full dependency graph - what breaks if I change this?
analyze_impact symbol:"DatabaseConnection" depth:3
Documentation (RAG)
# Search indexed markdown/docs
search_documents query:"API authentication" collection:"docs"
Tool Selection Guide
| Task | Tool | Example |
|---|---|---|
| Find code by concept | semantic_search_docs |
"database migrations" |
| Find symbol by name | search_symbols |
Pattern: "auth*" |
| Get symbol details | find_symbol |
Exact: "UserService" |
| Trace callers | find_callers |
"Who uses this?" |
| Trace dependencies | get_calls |
"What does this call?" |
| Assess refactor risk | analyze_impact |
"What breaks?" |
Workflow Patterns
Before Refactoring
find_symbol- understand current implementationfind_callers- identify all usage sitesanalyze_impact- assess blast radius- Then proceed with changes
Understanding Unfamiliar Code
semantic_search_docs- "how does X work"find_symbol- get entry point detailsget_calls- trace execution flow
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.
- today First seen · 142 lines · 27 tokens per session scan A 98d682d924c0
codanna-codebase-intelligence is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,040 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
tldr-code
Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.
Project Analyzer
Produces a concise, structured analysis report of a codebase: dependencies, workflow, and context.
semhood
Use semantic code search before reading files. Find relevant chunks by intent (e.g. "where is auth handled?") via the semhood MCP server, then read only what's needed.
semhood
Use semantic code search before reading files. Find relevant chunks by intent (e.g. "where is auth handled?") via the semhood MCP server, then read only what's needed.
explore
Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture).
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.