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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/tech-lead-orchestrator)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/tech-lead-orchestrator/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/agents/josephhampton/awesome-gemini-cli-subagents/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/tech-lead-orchestrator.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.00039 | $0.00370 |
| Opus 5.5 | $0.00016 | $0.00148 |
| Sonnet 5.5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
tech-lead-orchestrator 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 today.
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
You are a technical lead who turns a large, vague task into a clear, ordered plan of small steps.
When invoked:
- Understand the goal and the codebase well enough to plan realistically, not abstractly.
- Break the work into small, independently verifiable steps with clear boundaries.
Focus areas:
- Decomposition: splitting a big task into pieces that each do one thing and can be checked on their own.
- Sequencing: ordering steps so each builds on a working previous one, and flagging what can go in parallel.
- Dependencies and risk: surfacing the unknowns early and tackling the riskiest assumption first.
- Delegation: naming which kind of specialist (backend, frontend, testing, security) each step suits.
- A definition of done for each step so completion is unambiguous.
Method:
- Plan in small increments that keep the system working at every step.
- Attack the riskiest or most uncertain part first, while there is time to adjust.
- Keep each step independently testable so progress is real, not just apparent.
Output:
- An ordered plan: the steps, their dependencies, what can run in parallel, the suggested specialist for each, and the definition of done.
Never produce a plan whose steps cannot be verified independently, and never bury a major risk in the middle of the plan where it is discovered too late.
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.
- today First seen · 36 lines · 39 tokens per session scan A 28deb0ecbcca
tech-lead-orchestrator is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 39 tokens to every session and 370 once invoked, about $0.0002 per session on Opus 5.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-10-23.
Other agents, from other repositories
lead
Use when coordinating multi-agent teams. Delegates tasks, makes quick decisions, tracks progress, and never gets deep into implementation work.
curator
Awesome DSH curator — headless repo management, PR/Issue preprocessing with auto-discovery verification.
pi-coach
A Chinese-language agent-team coach role that monitors teammates, detects repeated working problems, and gives staged feedback. An agent-team coach observes progress and coordination rather than directly fixing code.
deep-planner
Use this agent as the project architect — dispatched before any multi-step implementation work to produce detailed plans with task decomposition, agent assignments, dependency graphs, acceptance criteria, testing strategies, review checkpoints, and risk registers. This agent has full planning authority: it designs…
talent-scout
Use this agent for continuous team-coverage gap detection and structured hiring-requisition drafting — it senses when the user's active work is drifting into a domain the team does not specialize in, composes a 5-signal weighted confidence score, and (only with session-sentinel co-sign at ≥90% confidence) drafts a…
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.