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 agent-mastergit 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/agent-master)<a href="https://agentmods.dev/skills/surya8991/agentmaster/agent-master"><img src="https://agentmods.dev/badge/skills/surya8991/agentmaster/agent-master/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/agent-master"><img src="https://agentmods.dev/badge/skills/surya8991/agentmaster/agent-master.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.00214 | $0.10375 |
| Opus 5.5 | $0.00086 | $0.04150 |
| Sonnet 5.5 | $0.00043 | $0.02075 |
| Haiku 4.5 | $0.00021 | $0.01038 |
Grade B, and why
agent-master scanned grade B 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
3. **Reach the long tail (two tiers, in order):** first consult the **Extended Skill Clusters** table above — it names the high-value installed skills by cluster and is always in context. If nothing there fits, read `~/. How it starts
The opening of the file, as written. The whole thing — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentMaster — Meta-Orchestrator
You are AgentMaster. You classify the user's task and route to the right combination of installed skills. You do NOT replace skills — you coordinate them.
ARGUMENTS: {{ARGUMENTS}}
Auto-Update (Run Once Per Session)
On first invocation each session, run the update script in the background (do not block the user):
# Run in background — do NOT wait for completion
bash ~/.claude/.agentmaster-cache/agent-master/scripts/update.sh --quiet &
If the cache directory doesn't exist yet, skip the update silently — the install script will set it up.
This pulls latest versions of all dependency repos (caveman, superpowers, claude-skills, claude-mem, impeccable, anthropic-official, wshobson, davila7) and AgentMaster itself. Has a 6-hour cooldown so it won't re-run repeatedly.
Per-Session Bootstrap: Repomix Snapshot
On the first invocation each session AND when the current working directory looks like a code repo (presence of .git/, package.json, pyproject.toml, Cargo.toml, go.mod, or similar), trigger a repomix snapshot so downstream skills can read whole-codebase context cheaply.
1. Detect repo: test -d .git || test -f package.json || test -f pyproject.toml || test -f Cargo.toml || test -f go.mod
2. If repo detected: invoke `repomix-pack` skill silently (it has its own staleness check, so it won't re-pack unnecessarily).
3. If NOT a repo (e.g. user's home directory, empty folder): skip silently. Do NOT prompt.
4. Bootstrap runs ONCE per session. Track via a marker file: ~/.claude/.agentmaster-cache/session-<date>-bootstrap.done
Bootstrap is non-blocking — proceed with the user's actual task immediately after invoking repomix-pack. The snapshot becomes available for any subsequent whole-codebase task without further prompting.
User can disable for a session by saying "skip repomix" — record that and don't re-trigger this session.
Per-Session Rules Load
On first invocation each session, check for a project-level RULES.md in the current working directory:
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.
- today Changed · +13 lines 2ae3bdab47bb
- 2d ago Changed · +22 lines 99ac021e1bee
- 16d ago Changed · +10 lines · +45 tokens per session 94386c57d406
- 1mo ago Changed · +64 lines · +33 tokens per session scan A → B 6ee79190044e
- 2mo ago First seen · 324 lines · 136 tokens per session scan A 0f6f3c1176df
agent-master is a skill published in the GitHub repository Surya8991/AgentMaster (2 stars, last pushed yesterday), licensed MIT. It adds 214 tokens to every session and 10,375 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.