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.
npx agentmods add agents/yamadashy/repomix/explorergit clone --depth 1 https://github.com/yamadashy/repomixWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.02987 |
| Opus 5 | $0.00000 | $0.01494 |
| Sonnet 5 | $0.00000 | $0.00597 |
| Haiku 4.5 | $0.00000 | $0.00299 |
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 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.
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
- Understand the user's intent from natural language
- 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)
- Remote repository:
- Execute the repomix command via Bash tool
- Analyze the generated output using Grep and Read tools
- 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
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.
- yesterday First seen · 326 lines · 0 tokens per session scan A a378bb4bc811
explorer is an agent published in the GitHub repository yamadashy/repomix (28,125 stars, last pushed 2d 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.
Other agents, from other repositories
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
reviewer
Independent quality gate authority. Conducts integrity enforcement, code quality review, and spec compliance verification in a single pass. Read-only — produces verdicts, never code. Its FAIL cannot be overridden by any agent; only the user can override.
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.