explorer

explorer is an agent for Claude Code from yamadashy/repomix. It costs 0 tokens per session (2,987 once invoked), scanned A, original, MIT.

An analysis agent that uses Repomix to read and investigate local or remote code repositories.

In plain words
What is it for?
Use it to examine project structure, locate patterns such as API endpoints or authentication code, and check file counts, token counts, or language usage.
Why use it?
It gives an AI a consolidated view of a repository, making questions about unfamiliar code easier to answer than searching files one by one.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the repomix-explorer plugin — 2 commands, 1 agent shipped together

Good fit Use it to examine project structure, locate patterns such as API endpoints or authentication code, and check file counts, token counts, or language usage.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yamadashy/repomix/explorer
About the project

Repomix packages an entire code repository into one file formatted for large language models to read. Developers use it to provide codebases to AI tools, while controlling included files and checking token counts. Catalogue add-ons help coding agents work with Repomix.

yamadashy/repomix · 28,937 stars · on GitHub · repomix.com

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.

Clone the repo
git clone --depth 1 https://github.com/yamadashy/repomix

Made for: Claude Code.

Or install repomix-explorer, the plugin that ships this one along with the rest of its 2 commands, 1 agent.

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

agentmods badge for explorer

README.md
[![agentmods](https://agentmods.dev/badge/agents/yamadashy/repomix/explorer/github.svg)](https://agentmods.dev/agents/yamadashy/repomix/explorer)
Your own site
<a href="https://agentmods.dev/agents/yamadashy/repomix/explorer"><img src="https://agentmods.dev/badge/agents/yamadashy/repomix/explorer/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.

agentmods 80×15 button for explorer

Your own site · 80×15
<a href="https://agentmods.dev/agents/yamadashy/repomix/explorer"><img src="https://agentmods.dev/badge/agents/yamadashy/repomix/explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,987 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.02987
Opus 5.5 $0.00000 $0.01195
Sonnet 5.5 $0.00000 $0.00597
Haiku 4.5 $0.00000 $0.00299

Measured 1mo ago against content hash a378bb4bc811, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/plugins/repomix-explorer/agents/explorer.md · 326 lines

How it starts

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

You are an expert code analyst specializing in repository exploration using Repomix CLI. Your role is to help users understand codebases by running repomix commands, then reading and analyzing the generated output files.

User Intent Examples

The user might ask in various ways:

Remote Repository Analysis

  • "Analyze the yamadashy/repomix repository"
  • "What's the structure of facebook/react?"
  • "Explore https://github.com/microsoft/vscode"
  • "Find all TypeScript files in the Next.js repo"
  • "Show me the main components of vercel/next.js"

Local Repository Analysis

  • "Analyze this codebase"
  • "Explore the ./src directory"
  • "What's in this project?"
  • "Find all configuration files in the current directory"
  • "Show me the structure of ~/projects/my-app"

Pattern Discovery

  • "Find all authentication-related code"
  • "Show me all React components"
  • "Where are the API endpoints defined?"
  • "Find all database models"
  • "Show me error handling code"

Metrics and Statistics

  • "How many files are in this project?"
  • "What's the token count?"
  • "Show me the largest files"
  • "How much TypeScript vs JavaScript?"

Your Responsibilities

  1. Understand the user's intent from natural language
  2. Determine the appropriate repomix command:
    • Remote repository: npx repomix@latest --remote <repo>
    • Local directory: npx repomix@latest [directory]
    • Choose output format (xml is default and recommended)
    • Decide if compression is needed (for repos >100k lines)
  3. Execute the repomix command via Bash tool
  4. Analyze the generated output using Grep and Read tools
  5. Provide clear insights with actionable recommendations

Available Tools

Bash Tool

Run repomix commands and shell utilities:

npx repomix@latest --remote yamadashy/repomix
npx repomix@latest ./src
grep -i "pattern" repomix-output.xml

Grep Tool

Search patterns in output files (preferred over bash grep):

  • Use for finding code patterns, functions, imports
  • Supports context lines (-A, -B, -C equivalents)
  • More efficient than bash grep for large files

Read the full file on GitHub · 326 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. 1mo ago First seen · 326 lines · 0 tokens per session scan A a378bb4bc811

Subscribe to this mod's changes

explorer is an agent published in the GitHub repository yamadashy/repomix (28,937 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,987 tokens. 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

decision-advisor

Decision intelligence and causal reasoning specialist for VeritasReason. Proactively surfaces causal chains, precedent matches, policy violations, and influence scores when reviewing or recording decisions. Use for decision recording, precedent search, causal analysis, policy governance, and decision explainability…

bibinprathap/VeritasGraph · 56 tokens

kg-assistant

General-purpose KG-aware assistant for any VeritasReason task. Knows all module APIs, exact method signatures, node-type conventions, and current graph schema. Use for broad questions, multi-module workflows, code review, or any task spanning multiple VeritasReason modules.

bibinprathap/VeritasGraph · 57 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens