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/madebyaris/advance-minimax-m3-cursor-rulesWrote 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/madebyaris/advance-minimax-m3-cursor-rules/cursor-agent-orchestration)<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/cursor-agent-orchestration"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/cursor-agent-orchestration/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/madebyaris/advance-minimax-m3-cursor-rules/cursor-agent-orchestration"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/cursor-agent-orchestration.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.00039 | $0.01610 |
| Opus 5 | $0.00019 | $0.00805 |
| Sonnet 5 | $0.00008 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
cursor-agent-orchestration 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 11d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor 3.7 Agent Orchestration
Current through Cursor 3.7 (Jun 2026). Use this rule for deep or exhaustive tasks where coordination matters more than raw implementation speed.
Core Idea
The main agent should own synthesis. Plans, subagents, and task tracking exist to reduce context load and make large work safer. On M3, the main agent also owns the 1M-context loader — see minimax-m3-long-context.
Local, worktree, cloud, and SSH sessions
Cursor 3.7 emphasizes moving work between execution environments inside the Agents Window. Treat this as workflow guidance, not a requirement:
- Prefer local when you need fast edit–run–debug loops, full filesystem access, or machine-specific verification.
- Prefer /worktree (isolated git worktree) when the task must not collide with the main tree, when you are running parallel branches, or when you want a disposable environment.
- Consider cloud when a task should keep running while you are away, or when you want continuation without tying up the local machine — then hand back to local to validate on the real environment when claims are environment-specific.
- Consider SSH when the runtime is on a remote host (e.g. an edge box, a build farm, a server) and the work needs direct access.
Handoffs should still use explicit goals, owned paths, environment, model, and what was verified (see agent-teams.mdc).
Parallel sessions and the sidebar
Cursor 3.7 can show many agent sessions at once (including from other surfaces — mobile, web, Slack, GitHub, Linear). That mirrors the idea of concurrent Task / subagent delegation: only parallelize independent slices, merge results in one synthesis step, and avoid two sessions racing the same files. The UI makes parallelism easier; it does not remove the need for clear ownership, non-overlapping paths, and one synthesis step.
When to Plan
Plan when:
- the task is ambiguous
- multiple valid approaches exist
- many files or systems will change
- the user needs approval before implementation
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.
- 11d ago First seen · 142 lines · 39 tokens per session scan A 27d5e2097106
cursor-agent-orchestration is a cursor rule published in the GitHub repository madebyaris/advance-minimax-m3-cursor-rules (125 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,610 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 cursor rules, from other repositories
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
learnship
Activate learnship agentic engineering workflows — structured phases, persistent memory, learning partner, and impeccable UI design. Use whenever a user is working on a software project or asks about project planning, phases, workflows, or how to build something.
behavior-principles
Global behavioral principles for all AI-assisted work in this repository. Covers thinking before coding, simplicity, surgical changes, goal-driven execution, and communication standards.
coding
Core coding behavior for this repository. Always prefer cautious, minimal, reversible changes.
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
workflow
Workflow canonical adapter and intent routing rules.