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 Surya8991/AgentMaster --skill repomix-packgit clone --depth 1 https://github.com/Surya8991/AgentMasterWrote 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/surya8991/agentmaster/repomix-pack)<a href="https://agentmods.dev/skills/surya8991/agentmaster/repomix-pack"><img src="https://agentmods.dev/badge/skills/surya8991/agentmaster/repomix-pack/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/surya8991/agentmaster/repomix-pack"><img src="https://agentmods.dev/badge/skills/surya8991/agentmaster/repomix-pack.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.00091 | $0.01085 |
| Opus 5.5 | $0.00036 | $0.00434 |
| Sonnet 5.5 | $0.00018 | $0.00217 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
repomix-pack 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 16d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repomix Pack — Whole-Codebase Snapshot
You are the repomix bridge skill. Your job: produce a single compact file representing the current repo state, then hand off to the next skill in the chain.
ARGUMENTS: {{ARGUMENTS}}
When to Use
Invoke this skill when ANY of these signal words appear:
- "entire codebase", "whole repo", "across the project", "all files"
- "full audit", "full security scan", "architecture review"
- "onboard me to this repo", "understand this codebase"
- "refactor X across the codebase", "find all usages of"
- Whenever
security-auditorcodereviewis invoked on the repo as a whole (not a diff)
Do NOT use for:
- Single-file tasks (Read the file directly)
- Diff-based code review (use
codereviewon the diff) - Targeted exploration (use
smart-exploreinstead — AST-based, cheaper)
Preflight Check
# 1. Confirm repomix is installed
which repomix || npm install -g repomix
# 2. Confirm we're in a git repo (repomix works best with one)
git rev-parse --show-toplevel 2>/dev/null || echo "WARN: not a git repo"
If repomix is missing and npm is unavailable, abort and tell the user: "Install Node + repomix: npm install -g repomix".
Default Pack Command
# Pack to a stable path under the repo's .agentmaster/ dir
mkdir -p .agentmaster
repomix --style xml -o .agentmaster/codebase.xml \
--ignore "**/node_modules/**,**/dist/**,**/build/**,**/.next/**,**/coverage/**,**/*.lock,**/*.log,**/.agentmaster/**,**/.git/**"
If a .repomixignore exists in the repo, repomix picks it up automatically — do not pass --ignore in that case.
Argument Handling
| ARGUMENTS pattern | Action |
|---|---|
| empty | Pack the whole repo with default ignores (above) |
include <glob> |
repomix --include "<glob>" -o .agentmaster/codebase.xml --style xml |
remote <url> |
repomix --remote <url> --style xml -o .agentmaster/codebase.xml |
refresh |
Delete .agentmaster/codebase.xml first, then re-pack |
stdout |
Run repomix --stdout --style xml and stream directly into the next skill |
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.
- 16d ago Changed · -1 lines 3ac9213af697
- 1mo ago Changed 65b5b238abc1
- 2mo ago First seen · 109 lines · 91 tokens per session scan A cc4d8daa1858
repomix-pack is a skill published in the GitHub repository Surya8991/AgentMaster (2 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,085 once invoked, about $0.0004 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-31.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
tech-lead/code-review
A checklist-based method for examining code for correctness, security, performance, clarity, and ease of maintenance.
pre-push
Pre-push security and quality pipeline: secrets scan, then tests, lint and review. TRIGGER automatically whenever the user requests a git push: 'push my changes', 'push to origin', 'push this', 'push the code', 'commit and push', 'ship it', 'deploy to remote', 'deploy to prod/staging/production', or any git push…
skill-trigger-auditor
Audit whether skills, agents and slash commands route correctly and safely, and whether a trigger regression test is needed. Use before changing routing metadata or widening a description.
ijfw-cross-audit
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit.