codebase-explorer

A read-only agent that surveys an existing codebase and reports its structure, frameworks, modules, dependencies, and development tiers. It can also produce a Project Structure section for AGENTS.md.

In plain words
What is it for?
Use it to inspect a repository's directories and manifests, identify major components, and document the project's structure.
Why use it?
It gives a coding agent a factual map of an unfamiliar repository before implementation begins. It does not modify files or judge whether the design is good.

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/shrekshrek/project-workflow/codebase-explorer
Clone the repo
git clone --depth 1 https://github.com/shrekshrek/project-workflow
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 194 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.00053 $0.00194
Opus 5 $0.00026 $0.00097
Sonnet 5 $0.00011 $0.00039
Haiku 4.5 $0.00005 $0.00019

Measured yesterday against content hash c05b1ad3b59b, 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 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.

adapters/claude/agents/codebase-explorer.md · 18 lines

What it actually says

Response language: Match the calling skill's language. File paths, framework names, and dependency names stay as-is.

You are the Claude Code adapter for the canonical codebase-explorer.

Before surveying, read:

  1. ${CLAUDE_PLUGIN_ROOT}/docs/reviewers/codebase-explorer.md (read completely; canonical contract)
  2. the project root structure and relevant manifests
  3. existing AGENTS.md when the caller provides it for comparison

Follow the canonical explorer spec exactly. Report facts first, provide the requested ## Project Structure snippet, and do not edit files.

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 · 18 lines · 53 tokens per session scan A c05b1ad3b59b

Subscribe to this mod's changes

codebase-explorer is an agent published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 194 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.

Related

Other agents, from other repositories

red-team

Adversarial diff reviewer. Hunts correctness bugs AND flags cleanup (reuse, simplification, efficiency, altitude) in the changed code, then verifies each finding before reporting. Runs in an isolated context to eliminate author-evaluator bias. Use after implementation, before commit, or standalone to review any diff.…

KashZod/devloop · 94 tokens

review-plan

Reviews implementation plans for completeness, correctness, functional gaps, standards, regression risk, robustness, architectural gaps, and TDD quality. Use after a plan/tracker is drafted, in the /plan skill before any code, and again when /implement spawns it to re-gate a revised plan during convergence.

KashZod/devloop · 65 tokens

review-impl

Conformance gate. Verifies the implementation matches the plan, every acceptance criterion is met with quoted test evidence, tests are meaningful, and the suite still passes. Does not hunt correctness bugs, robustness gaps, standards violations, or cleanup, red-team owns those. Use after implementation chunks are…

KashZod/devloop · 67 tokens

gsd-phase-researcher

Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.

open-gsd/gsd-core · 41 tokens

APIDesigner

Generates API contracts (OpenAPI/GraphQL) for a feature.

attilaszasz/sdd-pilot · 20 tokens

executor

Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.

datit309/supergraph · 25 tokens