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 commands/yamadashy/repomix/explore-remotegit 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.00008 | $0.00589 |
| Opus 5 | $0.00004 | $0.00295 |
| Sonnet 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 3d 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.
- 3d 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,159 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 589 once invoked, about $0.0000 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-30.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
branch-review
Multi-dimensional LLM council review on the current local feature branch — pre-PR review. Same dimensions as /gflow:pr-council-review but reads git diff ..HEAD instead of a PR; never posts to GitHub. Wrapper around skills/pr-council-review/SKILL.md § 8 (branch mode).