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.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yamadashy/repomix/plugin install repomix-explorerWrote 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.
[](https://agentmods.dev/commands/yamadashy/repomix/explore-local)<a href="https://agentmods.dev/commands/yamadashy/repomix/explore-local"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/explore-local/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.
<a href="https://agentmods.dev/commands/yamadashy/repomix/explore-local"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/explore-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00007 | $0.00590 |
| Opus 5.5 | $0.00003 | $0.00236 |
| Sonnet 5.5 | $0.00001 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
explore-local 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze a local codebase using the repomix-explorer:explorer agent.
When the user runs this command, they want to explore and understand a local project's code structure, patterns, and content.
Note: This command is part of the repomix-explorer plugin, so the repomix-explorer:explorer agent is guaranteed to be available.
Usage
The user should provide a path to a local directory:
- Absolute path (e.g., /Users/username/projects/my-app)
- Relative path (e.g., ./src, ../other-project)
- Current directory (use "." or omit)
Your Responsibilities
- Extract directory path from the user's input (default to current directory if not specified)
- Convert relative paths to absolute paths if needed
- Launch the repomix-explorer:explorer agent to analyze the codebase
- Provide the agent with clear instructions about what to analyze
Example Usage
/explore-local
/explore-local ./src
/explore-local /Users/username/projects/my-app
/explore-local . - find all authentication-related code
What to Tell the Agent
Provide the repomix-explorer:explorer agent with a task that includes:
- The directory path to analyze (absolute path)
- Any specific focus areas mentioned by the user
- Clear instructions about what analysis is needed
Default instruction template:
"Analyze this local directory: [absolute_path]
Task: Provide an overview of the codebase structure, main components, and key patterns.
Steps:
1. Run `npx repomix@latest [path]` to pack the codebase
2. Note the output file location
3. Use Grep and Read tools to analyze the output incrementally
4. Report your findings
[Add any specific focus areas if mentioned by user]
"
Command Flow
- Parse the directory path from user input (default to current directory if not specified)
- Resolve to absolute path
- Identify any specific questions or focus areas from the user's request
- Launch the repomix-explorer:explorer agent with:
- The Task tool
- A clear task description following the template above
- Any specific analysis requirements
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.
- 1mo ago First seen · 73 lines · 7 tokens per session scan A 052d23212ad6
explore-local is a command published in the GitHub repository yamadashy/repomix (28,937 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 590 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.