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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/team-protocol)<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/team-protocol"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/team-protocol/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/boparaiamrit/skills-by-amrit/team-protocol"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/team-protocol.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.01254 | $0.01254 |
| Opus 5 | $0.00627 | $0.00627 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
team-protocol 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 9d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Council Protocol
Core Principle
Agents reason and write. The CLI manages structure. Never mix these responsibilities.
When to Activate Council Mode
Activate the council when:
- Task spans 3+ files or 2+ systems
- Task requires research before implementation
- Task benefits from independent specialist perspectives
- User requests: "start a council", "use team mode", "team session"
Architecture
ORCHESTRATOR (main session, stays lean ~10-15% context)
│
├── council CLI ──── STATE.md, BOARD.md, messages/, handoffs/, gates/
│
└── Task() spawns ── researcher, architect, planner, executor, reviewer
(each in fresh 200k context)
- Orchestrator uses CLI for all structural operations
- Orchestrator spawns agents via Task() with file paths
- Agents read files, execute their role, write handoff files
- CLI validates everything between agent runs
Council Presets
| Preset | Agents | Use When |
|---|---|---|
| Full (5) | researcher -> architect -> planner -> executor -> reviewer | Complex multi-module features |
| Rapid (3) | researcher -> executor -> reviewer | Small features, clear requirements |
| Debug (3) | investigator -> fixer -> verifier | Bug investigation |
| Architecture (3) | researcher -> architect -> reviewer | Design decisions |
| Refactoring (4) | researcher -> planner -> executor -> reviewer | Large-scale refactoring |
| Audit (3) | researcher -> mapper -> reviewer | Codebase audit |
Message Protocol
All messages created via CLI. No manual creation.
council message --to <agent> --task "<description>" --context "<file1>,<file2>"
- CLI assigns sequential numbering (
msg-001.md,msg-002.md, ...) - CLI enforces message format (From, To, Task, Context Files)
- Messages live in
.planning/council/messages/ - Orchestrator creates messages; agents read them
Handoff Protocol
Agents write handoffs. CLI validates them.
council handoff --validate handoff-NNN-agent.md
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.
- 9d ago First seen · 166 lines · 1,254 tokens per session scan A 0d159f446226
team-protocol is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 1,254 tokens to every session, about $0.0063 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.