A set of rules for dividing coding work among multiple agents with clear roles, file ownership, environments, and handoffs.

Organizing planning, exploration, implementation, and verification; assigning agents to separate work areas; and coordinating local, isolated, cloud, or remote sessions.

It reduces conflicting edits and unclear responsibility when several agents work at once. It also helps decide which work can run in parallel and which must be sequential.

agent-teams — Cursor rule for Cursor by madebyaris

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.

Clone the repo

git clone --depth 1 https://github.com/madebyaris/advance-minimax-m3-cursor-rules

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/agent-teams/github.svg)](https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/agent-teams)

Your own site

<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/agent-teams"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/agent-teams/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/agent-teams"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/agent-teams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 886 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00886
Opus 5	$0.00020	$0.00443
Sonnet 5	$0.00008	$0.00177
Haiku 4.5	$0.00004	$0.00089

Measured 13d ago against content hash 0153da23a50e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

agent-teams 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 13d 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.

.cursor/rules/agent-teams.mdc · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Teams (M3 + Cursor 3.7)

Use this rule when the work is best handled by multiple agents or explicitly separated roles.

Team Shape

Define roles before delegating: planner, explorer, implementer, verifier, or another bounded role.
Give each role a distinct objective, owned surface, and stopping point.
Do not create overlapping ownership without a clear reason.

Multiple concurrent Cursor sessions

Cursor 3.7 can run several agent sessions in parallel (for example from the Agents Window sidebar, or kicked off from mobile, web, Slack, GitHub, Linear). The same rules apply as for parallel roles or subagent branches: use parallel sessions only for independent workstreams, keep non-overlapping ownership of files and decisions, and serialize anything that would race the same artifact. More sessions visible at once does not make conflicting edits safer.

Multi-Environment Teams

When a single team spans environments (some roles local, some in /worktree, some in cloud, some over SSH):

The handoff contract must name the environment per role — local, worktree, cloud, or SSH — and the model per role.
Choose environments to remove file-system races: if two roles may touch the same artifact, pin both to the same isolated worktree or serialize the touch.
Prefer /worktree for any role whose output will be reviewed and possibly discarded. Prefer cloud for any role whose value is "keep working while I am away."
When one role's output feeds another role in a different environment, the handoff payload should include the file paths, branch, and any required state — not just a prose summary.

Handoff Contract

Every handoff should state:

current goal
which repo or workspace root when more than one is in play
environment (local / worktree / cloud / SSH) and model (e.g. MiniMax-M3, composer-2.5, auto)
files, dirs, or questions owned
findings or artifacts produced
open risks or assumptions
exact next step for the receiving role

Read the full file on GitHub · 80 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.

13d ago First seen · 80 lines · 40 tokens per session scan A 0153da23a50e

Subscribe to this mod's changes

agent-teams 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 40 tokens to every session and 886 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.

Building agents Code Generation Planning agentic-ai ai-coding ai-workflow cursor cursor-ide

git-commit

Use this when the user asks for a git commit, commit message, or commit command.

kyungseo/ai-workflow-harness · 18 tokens

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.

FavioVazquez/learnship · 48 tokens

agent-teams