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/alieismy/codex-three-layer-deliveryWrote 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/alieismy/codex-three-layer-delivery/03-collaboration-modes)<a href="https://agentmods.dev/rules/alieismy/codex-three-layer-delivery/03-collaboration-modes"><img src="https://agentmods.dev/badge/rules/alieismy/codex-three-layer-delivery/03-collaboration-modes.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.1 | $0.00360 | $0.00360 |
| Opus 5 | $0.00180 | $0.00180 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
03-collaboration-modes 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 7d 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.
What it actually says
Human-AI Collaboration Modes
Select the collaboration mode based on document risk, ambiguity, authority, and verification strength.
| Mode | Use when | Human effort | Agent effort |
|---|---|---|---|
| AI First | Template-based PRD sections, review tables, glossary cleanup, structured summaries | 20% review | 80% drafting |
| Human First | Business scope decisions, architecture trade-offs, standards authority, approval conclusions | 70% decision | 30% analysis |
| Pair Mode | Feasibility analysis, proposal comparison, detailed design, clause-level standards work | 50% | 50% |
Default to Pair Mode when the work has business, compliance, standards, or architecture consequences.
AI First Preconditions
- Scope is clear and bounded.
- Source material and existing templates are available.
- Output format and acceptance criteria are clear.
- Verification commands or document consistency checks exist.
Human First Triggers
- Business scope, approval responsibility, or standards authority is unresolved.
- Architecture boundaries or compliance constraints are disputed.
- Evidence is insufficient for a factual, regulatory, or standards claim.
- The decision could become an authoritative baseline.
Pair Mode Behavior
- Read and summarize relevant documents first.
- Propose a short plan with verification points for multi-document work.
- Draft or revise in narrow increments.
- Verify traceability and evidence after each meaningful step when practical.
Background or Parallel Work
Use background agents or parallel tasks only when the subtasks are isolated and can be verified independently. Keep write access scoped to the document sections or files required for the task.
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.
- 7d ago First seen · 42 lines · 360 tokens per session scan A 8881bb0ecb41
03-collaboration-modes is a cursor rule published in the GitHub repository alieismy/codex-three-layer-delivery (2 stars, last pushed 7d ago), licensed MIT. It adds 360 tokens to every session, about $0.0018 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
shard-doc
BMAD CORE Tool: Shard Document.
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, invoices, statements, regulatory documents, and PDF delivery. Covers report pages, absolute pixel layout, header/footer panels, common elements, verification…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.