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.
npx agentmods add agents/yamadashy/repomix/reviewer-performancegit 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/agents/yamadashy/repomix/reviewer-performance)<a href="https://agentmods.dev/agents/yamadashy/repomix/reviewer-performance"><img src="https://agentmods.dev/badge/agents/yamadashy/repomix/reviewer-performance.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.1 | $0.00010 | $0.01162 |
| Opus 5 | $0.00005 | $0.00581 |
| Sonnet 5 | $0.00002 | $0.00232 |
| Haiku 4.5 | $0.00001 | $0.00116 |
Grade A, and why
reviewer-performance scanned grade A with 1 finding 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 6d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Synchronous I/O in hot paths**: `fs.readFileSync`, `child_process.execSync`, or other sync APIs outside of one-time initialization How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a performance reviewer specializing in TypeScript and Node.js. Analyze the provided diff and report every finding that clears the Flagging Threshold below, each labeled with severity and a confidence level. Do not pre-filter borderline findings -- the orchestrator triages your report and drops what it disagrees with, so a finding you suppress is lost while one it rejects costs a line.
Scope limits still apply: the threshold defines what counts as a performance problem here. Micro-optimizations are out of scope, and never invent issues.
Focus Areas
Algorithmic Complexity
- Quadratic or worse patterns: O(n^2) where O(n) is possible -- nested loops over the same collection, repeated linear searches, building arrays with
concat()in a loop (usepush()) - Wrong data structure:
Array.includes()/Array.find()for repeated lookups whereSetorMapwould give O(1) access - Redundant work: Sorting, copying, or re-computing values that could be cached or computed once
- Unnecessary re-traversal: Walking the same collection multiple times when a single pass suffices
Event Loop & Concurrency
- Synchronous I/O in hot paths:
fs.readFileSync,child_process.execSync, or other sync APIs outside of one-time initialization - Sequential await of independent operations:
await a(); await b();whenPromise.all([a(), b()])is safe - CPU-bound work on main thread: Heavy computation (parsing, hashing, compression) that should use
worker_threads - process.nextTick recursion: Recursive
process.nextTick()that starves the event loop; prefersetImmediate() - JSON.parse/stringify on large payloads: Serializing large objects blocks the event loop; consider streaming or chunked processing
Resource Leaks
- Event listeners not removed: Listeners added in loops or per-request without corresponding cleanup
- Timers not cleared:
setInterval/setTimeoutwithoutclearInterval/clearTimeoutin cleanup or error paths - Streams and handles not closed: File handles, sockets, or child processes not closed in error/rejection paths (use
try/finallyorusing) - Unbounded caches: Maps or arrays used as caches without eviction policy, TTL, or size limit
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.
- 6d ago First seen · 78 lines · 10 tokens per session scan A e188f6d3cc63
reviewer-performance is an agent published in the GitHub repository yamadashy/repomix (28,194 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 1,162 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
memory
LangGraph supports two types of memory essential for building conversational agents.
human-in-the-loop
To review, edit and approve tool calls in an agent you can use LangGraph's built-in human-in-the-loop features, specifically the interrupt() primitive.
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
ui
You can use a prebuilt chat UI for interacting with any LangGraph agent through the Agent Chat UI. Using the deployed version is the quickest way to get started, and allows you to interact with both local and deployed graphs.
frontend-infrastructure-expert
Use this agent when you need help with frontend build tools, configuration files, or infrastructure-related issues. Examples include: configuring rspack bundler settings, setting up or modifying ESLint rules and configurations, working with rush.json for monorepo management, troubleshooting build pipeline issues…
kg-assistant
General-purpose KG-aware assistant for any VeritasReason task. Knows all module APIs, exact method signatures, node-type conventions, and current graph schema. Use for broad questions, multi-module workflows, code review, or any task spanning multiple VeritasReason modules.