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 skills add spideynolove/claude-dotfiles --skill repomixgit clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/skills/spideynolove/claude-dotfiles/repomix)<a href="https://agentmods.dev/skills/spideynolove/claude-dotfiles/repomix"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/repomix/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/skills/spideynolove/claude-dotfiles/repomix"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/repomix.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.00038 | $0.00940 |
| Opus 5 | $0.00019 | $0.00470 |
| Sonnet 5 | $0.00008 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
repomix 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repomix — Broad Codebase Context
When to invoke this skill
Invoke repomix before any task that requires whole-repository understanding:
- Writing specs or architecture docs that reference multiple directories
- 04-uiux planning stage (before IntentSpec, LayoutSpec, TokenSpec)
- Reviewing consistency across many files
- Answering "how does X work across the codebase" questions
- Onboarding to an unfamiliar codebase
Do not use for single-file edits, simple bug fixes, or tasks where you already have the relevant files open.
CLI usage (primary method)
# Pack current directory to XML (AI-optimized, default)
repomix
# Pack to markdown (human-readable)
repomix --style markdown -o repomix-output/summary.md
# Pack with compression (Tree-sitter, ~70% fewer tokens)
repomix --compress
# Pack remote repo
repomix --remote user/repo
repomix --remote user/repo --remote-branch main -o output.xml
# Use a config file
repomix --config repomix.config.json
MCP tools (optional — only when repomix is a persistent MCP server)
mcporter call repomix.* fails with "Unknown MCP server" unless repomix is registered in Claude Code's MCP settings as a persistent server (autoStart: true). By default it is not — use CLI above instead.
If repomix IS configured as a persistent MCP server (via settings.json), these tools are available:
| Tool | Use case |
|---|---|
pack_codebase |
Pack a local directory — returns outputFilePath, use that not outputId |
pack_remote_repository |
Pack a GitHub repo by URL or user/repo shorthand |
grep_repomix_output |
Search packed output (persistent server only) |
Config file format
Create repomix.config.json in the project root:
{
"output": {
"filePath": "repomix-output/repo.xml",
"style": "xml",
"compress": false,
"removeComments": false,
"showLineNumbers": false,
"fileSummary": true,
"directoryStructure": true
},
"ignore": {
"useGitignore": true,
"useDotIgnore": true,
"customPatterns": ["repomix-output/**", "*.lock", "dist/**", "node_modules/**"]
},
"tokenCount": {
"encoding": "o200k_base"
}
}
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.
- 8d ago First seen · 113 lines · 38 tokens per session scan A 607edc4d6941
repomix is a skill published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 940 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…