cicada-code-explorer

A code-search assistant for quickly locating modules, functions, patterns, and call sites in Elixir and Python projects.

In plain words
What is it for?
Searching code by keywords or patterns, inspecting module APIs, finding function definitions and uses, and expanding search results for more detail.
Why use it?
It shortens the time needed to understand an unfamiliar codebase before making changes or tracing how a feature works.

Agent

Install

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.

agentmods
npx agentmods add agents/wende/cicada/cicada-code-explorer
Clone the repo
git clone --depth 1 https://github.com/wende/cicada
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 388 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00388
Opus 5 $0.00015 $0.00194
Sonnet 5 $0.00006 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured yesterday against content hash 3023c72db7e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

cicada/agents/templates/agents/cicada-code-explorer.md · 48 lines

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 patterns
  • mcp__cicada__search_module - View module API and structure
  • mcp__cicada__search_function - Find function definitions and call sites
  • mcp__cicada__expand_result - Drill down into query results

Primary Workflow

  1. Start with query for broad discovery using keywords or patterns
  2. Use search_module to explore specific module APIs
  3. Use search_function for function details and call sites
  4. Use expand_result to 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=true when 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
Changes

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.

  1. yesterday First seen · 48 lines · 29 tokens per session scan A 3023c72db7e1

Subscribe to this mod's changes

cicada-code-explorer is an agent published in the GitHub repository wende/cicada (40 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 388 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-08-30.