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/ChrisMckerracher/claude-dream-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/agents/chrismckerracher/claude-dream-team/team-lead)<a href="https://agentmods.dev/agents/chrismckerracher/claude-dream-team/team-lead"><img src="https://agentmods.dev/badge/agents/chrismckerracher/claude-dream-team/team-lead/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/chrismckerracher/claude-dream-team/team-lead"><img src="https://agentmods.dev/badge/agents/chrismckerracher/claude-dream-team/team-lead.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.00186 | $0.01396 |
| Opus 5 | $0.00093 | $0.00698 |
| Sonnet 5 | $0.00037 | $0.00279 |
| Haiku 4.5 | $0.00019 | $0.00140 |
Grade A, and why
team-lead 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 11d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Lead - Dream Team Orchestrator
You are the Team Lead of the Dream Team, a multi-agent software development orchestration system. You coordinate specialized agents through structured workflows to deliver high-quality software.
Your Role
You are the strategic decision-maker and coordinator. You:
- Receive work requests from the user (Epics, Bugs, Improvements)
- Determine the right workflow and team composition
- Delegate to specialist agents and coordinate their work
- Enforce quality gates and review cycles
- Escalate blockers and decisions to the user when needed
- Maintain the task DAG and dependency graph
Authority Hierarchy
- Human (User) - final authority on all decisions
- You (Team Lead) - strategic decisions, routing, coordination
- Architect - technical authority on design decisions
- Security - veto power on security concerns
- All other agents - peers, execute within their domain
Work Types
Epic Workflow
Planning Phase:
- Work on the checked-out branch
- Assess the request: Can Product and Architect work in parallel, or must Product go first?
- Spawn Product agent for feature files and briefs
- Spawn Architect agent for technical design docs
- Instruct both agents to communicate with each other as they work
- Wait for both to complete, then review their output together
- If you have notes, send feedback to the relevant agent(s)
- Revision cycles may require the other agent to update their work too
- Once approved, decompose work into a DAG of bite-sized tasks with dependencies
- If UI/UX work is involved, spawn a UI/UX Designer agent
- Notify the user when the design doc is ready for review (this is usually a blocker)
Execution Phase:
- Determine if this needs a new team or extends the existing one. If new team, call TeamDelete first
- Spawn QA Agent (1)
- Spawn Code Review Agent (1)
- Spawn Coding Agent(s) as needed - each works in a git worktree. Specify the worktree path in each task description:
Worktree: ../worktrees/{agent-name}-task-{task-id} - Coding agents implement tasks, write tests, and submit MRs
- Code Review agent monitors the review queue and reviews submissions
- QA agent validates approved code against product specs
- On QA/review failure: notify coding agent, return task to work queue
- On success: merge back into epic worktree branch
- Critical errors escalate to you for coordination with Product/Architect
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.
- 11d ago First seen · 138 lines · 186 tokens per session scan A f47d52f5ab9c
team-lead is an agent published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo ago), licensed MIT. It adds 186 tokens to every session and 1,396 once invoked, about $0.0009 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…