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/pack-local)<a href="https://agentmods.dev/commands/yamadashy/repomix/pack-local"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/pack-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/pack-local"><img src="https://agentmods.dev/badge/commands/yamadashy/repomix/pack-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.00008 | $0.00851 |
| Opus 5.5 | $0.00003 | $0.00340 |
| Sonnet 5.5 | $0.00002 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
pack-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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pack-remote — 91% identical, 69 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pack a local codebase using Repomix with AI-optimized format.
When the user asks to pack a local codebase, analyze their request and run the appropriate repomix command.
User Intent Examples
The user might ask in various ways:
- "Pack this codebase"
- "Pack the src directory"
- "Pack this project as markdown"
- "Pack TypeScript files only"
- "Pack with compression and copy to clipboard"
- "Pack this project including git history"
Your Responsibilities
- Understand the user's intent from natural language
- Determine the appropriate options:
- Which directory to pack (default: current directory)
- Output format: xml (default), markdown, json, or plain
- Whether to compress (for large codebases)
- File patterns to include/ignore
- Additional features (copy to clipboard, include git diffs/logs)
- Execute the command with:
npx repomix@latest [directory] [options]
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--include-diffs: Include git diff output--include-logs: Include git commit history
Command Examples
Based on user intent, you might run:
# "Pack this codebase"
npx repomix@latest
# "Pack the src directory"
npx repomix@latest src/
# "Pack as markdown with compression"
npx repomix@latest --style markdown --compress
# "Pack only TypeScript and Markdown files"
npx repomix@latest --include "src/**/*.ts,**/*.md"
# "Pack and copy to clipboard"
npx repomix@latest --copy
# "Pack with git history"
npx repomix@latest --include-diffs --include-logs
Analyzing the Output
IMPORTANT: The generated output file can be very large and consume significant context.
If the user wants to analyze or explore the generated output:
- DO NOT read the entire output file directly
- USE an appropriate sub-agent to analyze the output
- The sub-agent will efficiently search and read specific sections using grep and incremental reading
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.
- 2mo ago First seen · 100 lines · 8 tokens per session scan A c0e245e4662d
pack-local is a command published in the GitHub repository yamadashy/repomix (29,074 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 851 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.