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/pack-remotegit 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/pack-remote)<a href="https://agentmods.dev/commands/yamadashy/repomix/pack-remote"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/pack-remote.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00990 |
| Opus 5 | $0.00004 | $0.00495 |
| Sonnet 5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
pack-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 4d 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.
This is a copy
91% identical to pack-local — 69 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch and analyze a GitHub repository using Repomix.
When the user asks to pack a remote repository, analyze their request and run the appropriate repomix command.
User Intent Examples
The user might ask in various ways:
- "Pack the yamadashy/repomix repository"
- "Analyze facebook/react from GitHub"
- "Pack https://github.com/microsoft/vscode"
- "Pack react repository with compression"
- "Pack only TypeScript files from the Next.js repo"
- "Analyze the main branch of user/repo"
Your Responsibilities
- Understand the user's intent from natural language
- Extract the repository information:
- Repository URL or owner/repo format
- Specific branch, tag, or commit (if mentioned)
- Determine the appropriate options:
- Output format: xml (default), markdown, json, or plain
- Whether to compress (for large codebases)
- File patterns to include/ignore
- Additional features (copy to clipboard)
- Execute the command with:
npx repomix@latest --remote <repo> [options]
Supported Repository Formats
owner/repo(e.g., yamadashy/repomix)https://github.com/owner/repohttps://github.com/owner/repo/tree/branch-namehttps://github.com/owner/repo/commit/hash
Available Options
--style <format>: Output format (xml, markdown, json, plain)--include <patterns>: Include only matching patterns (e.g., "src//*.ts,/*.md")--ignore <patterns>: Additional ignore patterns--compress: Enable Tree-sitter compression (~70% token reduction)--output <path>: Custom output path--copy: Copy output to clipboard
Command Examples
Based on user intent, you might run:
# "Pack yamadashy/repomix"
npx repomix@latest --remote yamadashy/repomix
# "Analyze facebook/react"
npx repomix@latest --remote https://github.com/facebook/react
# "Pack the develop branch of user/repo"
npx repomix@latest --remote https://github.com/user/repo/tree/develop
# "Pack microsoft/vscode with compression"
npx repomix@latest --remote microsoft/vscode --compress
# "Pack only TypeScript files from owner/repo"
npx repomix@latest --remote owner/repo --include "src/**/*.ts"
# "Pack yamadashy/repomix as markdown and copy to clipboard"
npx repomix@latest --remote yamadashy/repomix --copy --style markdown
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.
- 4d ago First seen · 107 lines · 8 tokens per session scan A 2c25cb9ca0e3
pack-remote is a command published in the GitHub repository yamadashy/repomix (28,180 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 990 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to pack-local, differing in 69 lines, and is treated as a copy.
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.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.