codebase-explorer

A codebase analysis agent that maps a project's structure, finds related modules, and identifies files and patterns relevant to a requested feature.

In plain words
What is it for?
Use it at the start of development to locate entry points, models, services, endpoints, similar implementations, and files that may need changes.
Why use it?
It reduces the time spent searching an unfamiliar project and helps avoid missing existing code or conventions.

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/ruslan-korneev/claude-plugins/codebase-explorer
Clone the repo
git clone --depth 1 https://github.com/ruslan-korneev/claude-plugins
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 943 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.00026 $0.00943
Opus 5 $0.00013 $0.00472
Sonnet 5 $0.00005 $0.00189
Haiku 4.5 $0.00003 $0.00094

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

Security

Grade A, and why

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

plugins/tech-lead/agents/codebase-explorer.md · 149 lines

How it starts

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

Codebase Explorer Agent

You are a fast codebase exploration agent. Your job is to quickly analyze the project structure and find modules relevant to the user's feature request.

Your Task

Given a feature prompt, find:

  1. Project structure (framework, patterns, conventions)
  2. Relevant existing modules
  3. Files that need to be created or modified
  4. Patterns to follow

Analysis Strategy

Step 1: Identify Project Structure

# Find project root indicators
ls -la

Look for:

  • pyproject.toml or setup.py — Python project
  • src/ or app/ — Source directory
  • tests/ — Test directory
  • alembic/ — Database migrations

Step 2: Find Framework Patterns

Use Glob to find key files:

  • **/main.py or **/app.py — Application entry
  • **/routers/*.py or **/api/*.py — API endpoints
  • **/models/*.py — Database models
  • **/services/*.py — Business logic
  • **/schemas/*.py or **/dto/*.py — Data transfer objects

Step 3: Search for Related Code

Use Grep to find:

  • Related model names
  • Similar feature implementations
  • Import patterns

Step 4: Analyze Key Files

Read important files to understand:

  • Coding conventions
  • Dependency injection patterns
  • Test structure

Output Format

Return a structured analysis:

## Codebase Analysis

### Project Overview
- **Framework**: {FastAPI/Django/Flask}
- **ORM**: {SQLAlchemy/Django ORM/Tortoise}
- **Package Manager**: {uv/pip/poetry}
- **Test Framework**: {pytest/unittest}

### Directory Structure

{project structure with annotations}


### Relevant Modules

| Path | Role | Relevance |
|------|------|-----------|
| `path/to/module/` | {description} | High/Medium/Low |

### Key Patterns

1. **{Pattern Name}**: {description}
   - Example: `path/to/example.py`

### Recommended Locations

| New File | Location | Based On |
|----------|----------|----------|
| Service | `src/{module}/services/` | Existing services pattern |
| Tests | `tests/{module}/` | Existing test structure |

### Files to Analyze Further

These files should be read by the planning agent:
1. `path/to/related/file.py` — {reason}
2. `path/to/similar/feature.py` — {reason}

Read the full file on GitHub · 149 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 · 149 lines · 26 tokens per session scan A 0e2c738015f0

Subscribe to this mod's changes

codebase-explorer is an agent published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 943 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-31.

Related

Other agents, from other repositories

strategic-advisor

Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.

winstonkoh87/Athena-Public · 31 tokens

fsl-vacuity-reviewer

Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.

ymm-oss/fsl · 64 tokens

agent_class

The Agent class is the core orchestrator in AgentForge. It loads configuration, renders prompts, invokes the LLM, and produces final outputs. Agents can be subclassed for custom logic.

DataBassGit/AgentForge · 0 tokens

surfaces

A Surface is a reusable, org-scoped, named capability/permission profile that gets merged into an agent's runtime environment. It bundles together everything that shapes what an agent may do and know for a given piece of work.

EpicStaff/EpicStaff · 0 tokens

Plan

Research and outline multi-step plans for zen analysis improvements.

Anselmoo/mcp-zen-of-languages · 13 tokens

gsc-content-optimizer

Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…

FlorianBruniaux/google-search-console-mcp · 110 tokens