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.
git clone --depth 1 https://github.com/cafreeman/foundry-mcpWrote 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/rules/cafreeman/foundry-mcp/codanna)<a href="https://agentmods.dev/rules/cafreeman/foundry-mcp/codanna"><img src="https://agentmods.dev/badge/rules/cafreeman/foundry-mcp/codanna/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/rules/cafreeman/foundry-mcp/codanna"><img src="https://agentmods.dev/badge/rules/cafreeman/foundry-mcp/codanna.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.01445 | $0.01445 |
| Opus 5.5 | $0.00578 | $0.00578 |
| Sonnet 5.5 | $0.00289 | $0.00289 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
codanna 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 2mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codanna MCP Tools - Primary Code Exploration Method
CRITICAL: Use Codanna Tools for ALL Code Analysis
When any request involves understanding, exploring, or analyzing code:
- ALWAYS start with Codanna tools before using grep/read_file
- Use semantic search first - it's more powerful than text-based search
- Chain tools together to build complete understanding
- Only fall back to basic tools if Codanna doesn't provide results
Required Tool Usage Patterns
🔍 EXPLORATION TRIGGERS
Use Codanna tools when user asks:
- "How does [feature] work?"
- "Where is [concept] implemented?"
- "What calls/uses [function]?"
- "Find all [pattern] in the code"
- "Analyze impact of changing [symbol]"
- "Understand [architectural concept]"
🚀 STANDARD WORKFLOW
Always follow this sequence:
- Start Investigation:
mcp_codanna_get_index_info(understand scope) - Find Concepts:
mcp_codanna_semantic_search_docs(natural language search) - Locate Symbols:
mcp_codanna_find_symbolormcp_codanna_search_symbols(exact/fuzzy search) - Map Relationships:
mcp_codanna_get_calls+mcp_codanna_find_callers(dependencies) - Assess Impact:
mcp_codanna_analyze_impact(change planning)
🎯 TOOL SELECTION LOGIC
For conceptual questions → mcp_codanna_semantic_search_docs
- "authentication flow", "error handling patterns", "validation logic"
For specific symbols → mcp_codanna_find_symbol
- Known function/struct/trait names
For fuzzy exploration → mcp_codanna_search_symbols
- Partial names, exploring patterns, filtering by type
For understanding behavior → mcp_codanna_get_calls
- "What does this function do internally?"
For impact analysis → mcp_codanna_find_callers + mcp_codanna_analyze_impact
- "What would break if I change this?"
MANDATORY Usage Rules
✅ DO THIS:
- Start EVERY code exploration with
mcp_codanna_get_index_info - Use semantic search with descriptive queries: "HTTP request parsing with validation"
- Chain tools: semantic_search → find_symbol → get_calls → find_callers
- Use lower thresholds (0.3-0.4) for broader semantic search results
- Explain your tool choices to the user
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.
- 2mo ago First seen · 170 lines · 1,445 tokens per session scan A 0aee8377fb91
codanna is a cursor rule published in the GitHub repository cafreeman/foundry-mcp (4 stars, last pushed 7mo ago), licensed MIT. It adds 1,445 tokens to every session, about $0.0058 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-31.
Other cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.