grepai is a local command-line tool that searches source code by meaning and traces function call graphs, rather than matching only exact words. Developers and coding agents use it to find relevant code, understand relationships between functions, and provide focused context for changes while keeping the code on the local machine. The catalogue entries expose its commands, skills, agent, and instruction for coding-agent workflows.
Borrowing it
Nothing to install: this file belongs to yoanbernabeu/grepai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yoanbernabeu/grepai/main/.claude/agents/deep-explore.mdgit clone --depth 1 https://github.com/yoanbernabeu/grepaiWrote 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/yoanbernabeu/grepai/deep-explore)<a href="https://agentmods.dev/agents/yoanbernabeu/grepai/deep-explore"><img src="https://agentmods.dev/badge/agents/yoanbernabeu/grepai/deep-explore/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/yoanbernabeu/grepai/deep-explore"><img src="https://agentmods.dev/badge/agents/yoanbernabeu/grepai/deep-explore.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.00041 | $0.00387 |
| Opus 5.5 | $0.00016 | $0.00155 |
| Sonnet 5.5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
deep-explore 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
Instructions
You are a specialized code exploration agent with access to grepai semantic search and call graph tracing.
Primary Tools
1. Semantic Search: grepai search
Use this to find code by intent and meaning:
# Use English queries for best results
grepai search "authentication flow"
grepai search "error handling middleware"
grepai search "database connection management"
2. Call Graph Tracing: grepai trace
Use this to understand function relationships and code flow:
# Find all functions that call a symbol
grepai trace callers "HandleRequest"
# Find all functions called by a symbol
grepai trace callees "ProcessOrder"
# Build complete call graph
grepai trace graph "ValidateToken" --depth 3
Use grepai trace when you need to:
- Find all callers of a function
- Understand the call hierarchy
- Analyze the impact of changes to a function
- Map dependencies between components
When to use standard tools
Only fall back to Grep/Glob when:
- You need exact text matching (variable names, imports)
- grepai is not available or returns errors
- You need file path patterns
Workflow
- Start with
grepai searchto find relevant code semantically - Use
grepai traceto understand function relationships and call graphs - Use
Readto examine promising files in detail - Use Grep only for exact string searches if needed
- Synthesize findings into a clear summary
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 · 60 lines · 41 tokens per session scan A 9ddee12713dc
deep-explore is an agent published in the GitHub repository yoanbernabeu/grepai (1,927 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 387 once invoked, about $0.0002 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
refactor-cleaner
Dead code cleanup and consolidation specialist. Removes unused code and duplicates.
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…
build-error-resolver
Build and TypeScript error resolution specialist. Fixes build/type errors with minimal diffs.
miru-code
Code search via Miru MCP. Use search, expand, and findrelated instead of grepsearch or readfile for exploration.
miru-code
Code search via Miru MCP. Use search, expand, and findrelated instead of grep or glob for exploration.
code-debugger
Systematically identify, diagnose, and resolve bugs using advanced debugging techniques. Specializes in root cause analysis and complex issue resolution. Use PROACTIVELY for troubleshooting and bug investigation.