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 agentmods add rules/jterratsdev/ableton-live-mcp/agent-collaborationgit clone --depth 1 https://github.com/jterratsdev/ableton-live-mcpWrote 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/jterratsdev/ableton-live-mcp/agent-collaboration)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/agent-collaboration"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/agent-collaboration.svg" alt="Measured on agentmods" 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 | $0.00877 | $0.00877 |
| Opus 5 | $0.00439 | $0.00439 |
| Sonnet 5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
agent-collaboration 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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Collaboration
Agents must collaborate through explicit artifacts and review checkpoints. Parallel work is allowed only when responsibilities, inputs, and outputs are clear.
Shared Context
- Start with a shared task brief: goal, backlog item, constraints, assumptions, risks, and definition of done.
- Confirm the GitHub issue exists and has been technically refined before starting each work block.
- Keep a visible decision log for architecture choices, scope cuts, security exceptions, and release trade-offs.
- Treat unresolved questions as blockers when they affect user value, data contracts, security, or deployment.
User Alignment Gate
- Before implementation, discuss the proposed solution and architecture with the user.
- Present the plan in concrete terms: scope, files or modules likely to change, domain/model changes, service/integration changes, controller/entry-point changes, data flow, risks, trade-offs, test strategy, and expected evidence.
- Do not start coding when the architecture, acceptance criteria, or user-visible behavior is ambiguous.
- If the task is a trivial mechanical edit, state that no architecture decision is involved and proceed with the smallest safe change.
- If new information invalidates the agreed plan, pause and realign with the user before continuing.
Collaboration Flow
- Product Owner and Analyst define acceptance criteria before Developer or QA treat the task as ready.
- Product Owner and Business Analyst must validate user stories, definitions, assumptions, acceptance criteria, non-goals, and priority with the user before approving the
po→architecthandoff. - If user validation is missing or scope is still ambiguous, keep the task in refinement, record the open question, and do not route it to Architect as ready-for-design.
- Architect and Security review designs before implementation when work touches boundaries, data, auth, infra, or external integrations.
- UX/UI Designer reviews user-facing flows before implementation when the task changes screens, copy, navigation, onboarding, or accessibility.
- SRE, DBA, Compliance/Privacy, and Release Manager review before release when reliability, database, regulatory, or rollout risk is material.
- Developer starts implementation only after the user alignment gate and required role reviews are complete.
- Developer shares implementation notes, unit test evidence, and changed behavior with QA, DevOps, and Security before final verification.
- QA, DevOps, and Security report release blockers back to Product Owner for go/no-go decisions.
- Developer work must pass through QA review before release approval.
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.
- 3d ago First seen · 61 lines · 877 tokens per session scan A 38a79bcf1431
agent-collaboration is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 10d ago), licensed MIT. It adds 877 tokens to every session, about $0.0044 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.
Other cursor rules, from other repositories
development-workflow
AAMAD modular development workflow for context-aware agent coordination.
checkpoint
Write a committed handoff checkpoint so a fresh session can resume with zero loss. Use when crossing the 40% context line, on every stage transition, and at session end. Writes .trace/checkpoints/ - .md while the agent is still sharp.
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
12-plan-ticket
Activates when the user says "create a ticket", "plan this ticket", "ticket for", or provides a plan doc and asks for a ticket template. Bucket 2 — reads local files only, no external services.