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 YPares/agent-skills --skill cursor-agent-supervisorgit clone --depth 1 https://github.com/YPares/agent-skillsWrote 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/ypares/agent-skills/cursor-agent-supervisor)<a href="https://agentmods.dev/skills/ypares/agent-skills/cursor-agent-supervisor"><img src="https://agentmods.dev/badge/skills/ypares/agent-skills/cursor-agent-supervisor.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00810 |
| Opus 5 | $0.00024 | $0.00405 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
cursor-agent-supervisor 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Supervisor
You can start subagents (e.g. to work on a specific JJ revision) with:
# Create a conversation with a sub-agent:
cursor-agent --print --model <model-name> create-chat # Prints a conversation uuid
# Give a task to the sub-agent: (command will finish when sub-agent is done)
cursor-agent --print --resume <conversation-uuid> "...description of the subagent's task..."
Model Selection
cursor-agent --print --model unknown-model will print an error that will list available models.
Unless you know which model is best for the task, just use sonnet-4.5 by default.
Invocation
Important: Sub-agent tasks can take several minutes. Always use a longer timeout:
# In your Shell tool call, set timeout to 10 minutes
timeout: 600000
The --print flag makes the sub-agent run on its own, and reply only once it is done.
Setting Things up for the Sub-agent
Prepare things up so the agent can focus on its task (eg. if using JJ, don't ask them to run jj commands unless really necessary.
Notably run jj edit yourself first to get into the revision where the work should be done).
Ideally, the sub-agent should only have to read your instructions, hack on code, run build/tests, hack on code, etc.
until your instructions are implemented, and then reply with a final answer.
YOU are in charge of bookkeeping, not them. YOU have the big picture, they don't.
Giving Good Instructions
Give the subagent the instructions they will need to complete the task, but do not overwhelm them.
Do:
- Provide a clear, specific goal
- List key files to read/modify
- Specify what "done" looks like
- Include relevant patterns to follow or reference implementations
- Tell them which skills to load if needed
Don't:
- Dump or link to entire skills when they only need a subset
- Include irrelevant context
- Leave success criteria ambiguous
Task Description Template
Work on [specific task] in [repo/directory].
**Setup:**
- Skills to load or files to read IN FULL
- Summarized instructions from skills or files, tailored to the task
**Goal:**
[Clear description of what to implement/fix]
**Key files:**
- path/to/main/file.ts - [why it matters]
- path/to/reference.ts - [pattern to follow]
**Requirements:**
- [Specific requirement 1]
- [Specific requirement 2]
**Done when:**
- [Testable criterion 1]
- [Testable criterion 2]
- [e.g., "pnpm -F @pkg lint passes"]
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 · 101 lines · 48 tokens per session scan A e9cddd040126
cursor-agent-supervisor is a skill published in the GitHub repository YPares/agent-skills (30 stars, last pushed 9d ago), licensed MIT. It adds 48 tokens to every session and 810 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-30.
Other skills, from other repositories
agent-rig-system
A rig is a collection of riglets that provide knowledge and tools for AI agents. Rigs and riglets are packaged as Nix flake outputs, so they can both be used inside the project defining them and by other projects depending on it.
riglet-creator
Creating effective riglets means writing knowledge (SKILL.md) that agents will rely on. This guide focuses on how to write high-quality documentation for riglets, organized efficiently.
nix-module-system
Practical knowledge about lib.evalModules that's hard to find in official docs.
code-search
Fast, efficient utilities for searching code and browsing file hierarchies.
Summarize document text and identify its main claims, evidence, and unanswered questions.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…