Borrowing it
Nothing to install: this file belongs to gosha70/code-copilot-team. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/team-lead-efficiency.instructions.mdgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/instructions/gosha70/code-copilot-team/team-lead-efficiency)<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/team-lead-efficiency"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/team-lead-efficiency.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.01809 | $0.01809 |
| Opus 5 | $0.00905 | $0.00905 |
| Sonnet 5 | $0.00362 | $0.00362 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
code-copilot-team team-lead-efficiency.instructions.md 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 — 143 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.
- 3d ago First seen · 143 lines · 1,809 tokens per session scan A 6788c39b9540
code-copilot-team team-lead-efficiency.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 1,809 tokens to every session, about $0.0090 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-09-03.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.