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/consiliency/code-index-mcp/search-codegit clone --depth 1 https://github.com/Consiliency/Code-Index-MCPWhat 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.00278 |
| Opus 5 | $0.00000 | $0.00139 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
search-code 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.
What it actually says
Search Code Patterns
Search for code patterns, text, or concepts across the entire codebase using the MCP index.
Use indexed results as authoritative only when repository readiness is ready.
If search_code returns index_unavailable with
safe_fallback: "native_search", use native rg/file search and follow the
readiness remediation, such as reindex.
Usage
/search-code <pattern> [options]
Examples
/search-code "def process_.*"- Find all process functions/search-code "class.*Plugin"- Find all plugin classes/search-code "error handling" semantic- Semantic search for error handling patterns/search-code "import torch"- Find all files importing torch
Options
semantic- Enable semantic search for concept querieslimit=N- Limit results (default: 10)
Implementation
This command uses mcp__code-index-mcp__search_code with these features:
- Regular expression support
- Semantic search with Voyage AI embeddings
- Context snippets with highlighting
- <500ms response time
Ready indexes return ordinary results: [] for no matches. Non-ready indexes
return index_unavailable, where native_search is expected until remediation
is complete.
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 · 34 lines · 0 tokens per session scan A 9e0f93cdff28
search-code is a command published in the GitHub repository Consiliency/Code-Index-MCP (57 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 278 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.