agent-master

A meta-orchestrator that classifies a request and routes it to suitable installed agent skills. It coordinates skills for areas such as development workflows, business tasks, concise output, and tactical libraries.

In plain words
What is it for?
Use it as a general entry point when a task may require several specialised skills or when you want the agent to select the routing.
Why use it?
It reduces the need to choose the right skill manually for each task. Its input describes automatic cache updates and code-repository snapshots as part of its setup process.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/surya8991/agentmaster/agent-master
Clone the repo
git clone --depth 1 https://github.com/Surya8991/AgentMaster

Made for: Cursor.

Per session 133 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,798 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00133 $0.06798
Opus 5 $0.00067 $0.03399
Sonnet 5 $0.00027 $0.01360
Haiku 4.5 $0.00013 $0.00680

Measured yesterday against content hash c38aa7e05720, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-master 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 yesterday.

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.

.cursor/rules/agent-master.mdc · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 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:

Read the full file on GitHub · 322 lines

Changes

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.

  1. yesterday First seen · 322 lines · 133 tokens per session scan A c38aa7e05720

Subscribe to this mod's changes

agent-master is a cursor rule published in the GitHub repository Surya8991/AgentMaster (2 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 6,798 once invoked, about $0.0007 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.