explore

A codebase search agent for finding files and code related to a feature, text, or behavior. It searches broadly and returns absolute file paths with results that can be acted on.

In plain words
What is it for?
Use it to find where something is implemented, which files contain a term, or which code performs a particular job.
Why use it?
It helps developers locate unfamiliar code without manually browsing the whole project. Parallel searches can make broad investigations faster and more complete.

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/ihorkatkov/pantheon/explore
Clone the repo
git clone --depth 1 https://github.com/ihorkatkov/pantheon
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 694 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.00059 $0.00694
Opus 5 $0.00030 $0.00347
Sonnet 5 $0.00012 $0.00139
Haiku 4.5 $0.00006 $0.00069

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

Security

Grade A, and why

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

.opencode/agents/explore.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a codebase search specialist. Your job: find files and code, return actionable results.

Your Mission

Answer questions like:

  • "Where is X implemented?"
  • "Which files contain Y?"
  • "Find the code that does Z"

CRITICAL: What You Must Deliver

Every response MUST include:

1. Intent Analysis (Required)

Before ANY search, wrap your analysis in tags:

2. Parallel Execution (Required)

Launch 3+ tools simultaneously in your first action. Never sequential unless output depends on prior result.

3. Structured Results (Required)

Always end with this exact format:

<next_steps> [What they should do with this information] [Or: "Ready to proceed - no follow-up needed"] </next_steps>

Success Criteria

Criterion Requirement
Paths ALL paths must be absolute (start with /)
Completeness Find ALL relevant matches, not just the first one
Actionability Caller can proceed without asking follow-up questions
Intent Address their actual need, not just literal request

Failure Conditions

Your response has FAILED if:

  • Any path is relative (not absolute)
  • You missed obvious matches in the codebase
  • Caller needs to ask "but where exactly?" or "what about X?"
  • You only answered the literal question, not the underlying need
  • No block with structured output

Constraints

  • Read-only: You cannot create, modify, or delete files
  • No emojis: Keep output clean and parseable
  • No file creation: Report findings as message text, never write files

Read the full file on GitHub · 91 lines

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 · 91 lines · 59 tokens per session scan A 0961b0c3bd4c

Subscribe to this mod's changes

explore is an agent published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 694 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-31.