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
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.
git clone --depth 1 https://github.com/yamadashy/repomixWrote 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-remote)<a href="https://agentmods.dev/commands/yamadashy/repomix/explore-remote"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/explore-remote/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-remote"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/explore-remote.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.00008 | $0.00589 |
| Opus 5.5 | $0.00003 | $0.00236 |
| Sonnet 5.5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
explore-remote 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze a remote GitHub repository using the repomix-explorer:explorer agent.
When the user runs this command, they want to explore and understand a remote repository'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 GitHub repository in one of these formats:
owner/repo(e.g., yamadashy/repomix)- Full GitHub URL (e.g., https://github.com/facebook/react)
- URL with branch (e.g., https://github.com/user/repo/tree/develop)
Your Responsibilities
- Extract repository information from the user's input
- Launch the repomix-explorer:explorer agent to analyze the repository
- Provide the agent with clear instructions about what to analyze
Example Usage
/explore-remote yamadashy/repomix
/explore-remote https://github.com/facebook/react
/explore-remote microsoft/vscode - show me the main architecture
What to Tell the Agent
Provide the repomix-explorer:explorer agent with a task that includes:
- The repository to analyze (URL or owner/repo format)
- Any specific focus areas mentioned by the user
- Clear instructions about what analysis is needed
Default instruction template:
"Analyze this remote repository: [repo]
Task: Provide an overview of the repository structure, main components, and key patterns.
Steps:
1. Run `npx repomix@latest --remote [repo]` to pack the repository
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 repository information from user input (owner/repo or full URL)
- 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 · 70 lines · 8 tokens per session scan A f79c49bc5679
explore-remote is a command published in the GitHub repository yamadashy/repomix (28,937 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 589 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
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
careful
Blocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE / TRUNCATE, kubectl delete and terraform or tofu destroy, including inside ssh remote commands, and makes Claude ask the…
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
reconcile
Establish git ground truth (branch, status, stashes, worktrees, ahead/behind) before any mutation, halt on protected or destructive operations, then carry the known-good state through a single-concern commit, a push, an open PR, and — after the PR merges — a fast-forward of the default branch. Enforces Law 1 (Research…