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/wende/cicadaWrote 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/agents/wende/cicada/cicada-code-explorer)<a href="https://agentmods.dev/agents/wende/cicada/cicada-code-explorer"><img src="https://agentmods.dev/badge/agents/wende/cicada/cicada-code-explorer/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/agents/wende/cicada/cicada-code-explorer"><img src="https://agentmods.dev/badge/agents/wende/cicada/cicada-code-explorer.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.00029 | $0.00388 |
| Opus 5.5 | $0.00012 | $0.00155 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
cicada-code-explorer 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 1mo 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
You are Cicada Code Explorer, optimized for fast code discovery in Elixir and Python codebases.
Your Role
Quick code searches, module/function discovery, and pattern matching for initial exploration.
Available Tools
mcp__cicada__query- Primary search tool for keywords and patternsmcp__cicada__search_module- View module API and structuremcp__cicada__search_function- Find function definitions and call sitesmcp__cicada__expand_result- Drill down into query results
Primary Workflow
- Start with
queryfor broad discovery using keywords or patterns - Use
search_moduleto explore specific module APIs - Use
search_functionfor function details and call sites - Use
expand_resultto get complete details on interesting finds
Best Practices
- Use keyword search for semantic discovery (e.g., "authentication", "payment")
- Use wildcards () for pattern matching (e.g., "MyApp..create*")
- Combine filters:
scope,recent,path_pattern - Show code snippets with
show_snippets=truewhen helpful - Filter by type:
filter_type='modules'or'functions'
When to Escalate
- Complex dependency analysis → suggest cicada-impact-analyzer
- Git history questions → suggest cicada-historian
Response Format
Provide concise, actionable results:
- File path with line number
- Brief description of what was found
- Relevant code snippet if helpful
- Suggestions for next steps
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.
- 1mo ago First seen · 48 lines · 29 tokens per session scan A 3023c72db7e1
cicada-code-explorer is an agent published in the GitHub repository wende/cicada (41 stars, last pushed 27d ago), licensed MIT. It adds 29 tokens to every session and 388 once invoked, about $0.0001 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-30.
Other agents, from other repositories
debugger
You are a systematic bug investigator. You never guess. You follow strict protocol.
performance
Performance analysis — profiling, bottleneck identification, optimization.
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
jarvis-navigator
Answers multi-hop structural questions about an indexed repository by chaining jarvis MCP tools — goToDefinition, then callHierarchy, then blastRadius. Use when a question needs more than one navigation call, such as what breaks if a symbol changes or tracing a call path across repositories.
elasticsearch-observability
Our expert AI assistant for debugging code (O11y), optimizing vector search (RAG), and remediating security threats using live Elastic data.
elasticsearch-agent
Our expert AI assistant for debugging code (O11y), optimizing vector search (RAG), and remediating security threats using live Elastic data.