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/gosha70/code-copilot-team/team-lead-efficiencygit clone --depth 1 https://github.com/gosha70/code-copilot-teamWhat 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.00023 | $0.01835 |
| Opus 5 | $0.00012 | $0.00918 |
| Sonnet 5 | $0.00005 | $0.00367 |
| Haiku 4.5 | $0.00002 | $0.00184 |
Grade A, and why
team-lead-efficiency 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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Lead Efficiency
Rules for the lead agent when coordinating sub-agents to minimize waste and maximize throughput.
Task Scoping
Right-Size the Work
- 2-3 teammates is the sweet spot for most features. More than 3 increases coordination overhead without proportional speedup.
- Each teammate task should take 5-30 minutes. If a task takes over an hour, it's too large — break it up.
- If a task would touch fewer than 3 files, the lead should do it directly instead of delegating.
Non-Overlapping Ownership
Every file must have exactly ONE owner for a given phase:
Bad:
Agent A: Implement product service (touches product model, router, UI)
Agent B: Implement order service (also touches product model for inventory)
Good:
Agent A: Implement product service (owns product.service, product.router)
Agent B: Implement order service (owns order.service, order.router)
Lead: Handles shared code (product model changes for inventory) after both complete
The lead handles shared/cross-cutting code after teammates return — not in parallel.
Clear Boundaries in the Delegation Prompt
Every delegation must include:
- Exact files to create or modify (not "implement the feature").
- Read-only context files — schema, types, design docs the agent should reference but NOT modify.
- Interface contracts — what inputs/outputs must match.
- What NOT to do — explicit exclusions prevent scope creep.
Polling Discipline
Do Not Busy-Wait on Teammates
After launching sub-agents, the lead should:
- Launch all independent agents at once (parallel, not sequential).
- Work on non-overlapping tasks while waiting (documentation, tests, review plans).
- Check status periodically — not continuously. Polling once per minute is sufficient.
- Never re-do teammate work. If a teammate is slow, wait or stop them — don't duplicate their output.
When to Stop a Teammate
Stop a running teammate if:
- Its task is no longer needed (requirements changed).
- The lead has already completed the work (this means the task was mis-delegated).
- The agent has been running over 2x the expected duration with no progress.
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.
- 2d ago First seen · 144 lines · 23 tokens per session scan A 9e5fc31116e8
team-lead-efficiency is a cursor rule published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,835 once invoked, about $0.0001 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.