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/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/rules/surya8991/agentmaster/agent-master)<a href="https://agentmods.dev/rules/surya8991/agentmaster/agent-master"><img src="https://agentmods.dev/badge/rules/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/rules/surya8991/agentmaster/agent-master"><img src="https://agentmods.dev/badge/rules/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.00166 | $0.08651 |
| Opus 5.5 | $0.00066 | $0.03460 |
| Sonnet 5.5 | $0.00033 | $0.01730 |
| Haiku 4.5 | $0.00017 | $0.00865 |
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 1mo 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.
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 — 386 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.
- 1mo ago Changed · +64 lines · +33 tokens per session scan A → B 454c8c5a0fdb
- 1mo ago First seen · 322 lines · 133 tokens per session scan A c38aa7e05720
agent-master is a cursor rule published in the GitHub repository Surya8991/AgentMaster (2 stars, last pushed 1mo ago), licensed MIT. It adds 166 tokens to every session and 8,651 once invoked, about $0.0007 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 cursor rules, from other repositories
optimize-dry-solid-principles-cursorrules-prompt-f
Cursor rules for optimization development with DRY and SOLID principles integration.
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
testing
Testing strategies and quality assurance — testing pyramid, unit/integration/E2E testing, TDD/BDD, test automation, and quality metrics. Applied when writing or reviewing tests.
advanced-patterns
Advanced patterns for Electron development — multi-window management, typed IPC, plugin architecture, security policies, performance monitoring, and error recovery. Applied when building complex Electron applications.
api-design-typescript
API Design for TypeScript — Express, NestJS, Fastify patterns, middleware, validation, and error handling. Extends core/rules/api-design.mdc with TypeScript-specific guidance.