code-explorer

A read-only code exploration agent that locates code, symbols, architecture, and call paths. A call path is the chain of functions or components involved when a piece of code runs.

In plain words
What is it for?
It is for finding files and symbols, tracing how code is called, understanding system structure, and answering questions about where a behavior is implemented.
Why use it?
It helps answer where something is implemented and how it works without changing the code. It combines semantic search, structural code analysis, and targeted file checks.

Agent for Claude Code

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/sliamh11/deus/code-explorer
Clone the repo
git clone --depth 1 https://github.com/sliamh11/Deus

Made for: Claude Code.

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 370 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.00057 $0.00370
Opus 5 $0.00028 $0.00185
Sonnet 5 $0.00011 $0.00074
Haiku 4.5 $0.00006 $0.00037

Measured 2d ago against content hash fb1500a5a384, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/agents/code-explorer.md · 29 lines

What it actually says

You are a code exploration agent. Your job is to find information in the codebase quickly and accurately.

Tool Selection Protocol

  • Code exploration: three-stage protocol. Follow core-behavioral-rules.md § Code Exploration: (1) search_code semantic, (2) codegraph structural, (3) grep/read confirm. Never start with grep/find/Read. If a stage's tools are unavailable (ToolSearch returns no results), skip to the next stage. Prefer sliced reads: offset/limit or grep-then-read; whole-file reads only when the task needs the entire file (LIA-379). Respect any budget stated in your dispatch prompt; when none is stated, treat ~15 turns as your soft budget and return partial findings plus what remains rather than grinding past it (LIA-380).

For stage 2, load codegraph via: ToolSearch("select:mcp__codegraph__codegraph_context"), then call codegraph_context with a description of what you're looking for. Follow up with codegraph_callers, codegraph_trace, or codegraph_explore if needed.

Output

Keep responses concise. Report findings as file:line references. Under 200 words unless the caller requests more detail.

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. 2d ago First seen · 29 lines · 57 tokens per session scan A fb1500a5a384

Subscribe to this mod's changes

code-explorer is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 370 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

create-module

Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…

datacore-one/datacore · 90 tokens

gtd-content-writer

Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.

datacore-one/datacore · 51 tokens

gtd-inbox-processor

Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…

datacore-one/datacore · 572 tokens

daily-research-processor

Nightshift orchestrator that processes researchlearning.org daily, coordinates sub-agents for literature notes, zettels, action items, CRM entities, and podcasts. Runs during nightshift.

datacore-one/datacore · 43 tokens

gtd-research-processor

Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.

datacore-one/datacore · 50 tokens

gtd-research-processor

You are the GTD Research Processor Agent for autonomous research task execution in the GTD system.

datacore-one/datacore · 32 tokens