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/commands/chrismckerracher/claude-dream-team/status)<a href="https://agentmods.dev/commands/chrismckerracher/claude-dream-team/status"><img src="https://agentmods.dev/badge/commands/chrismckerracher/claude-dream-team/status/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/commands/chrismckerracher/claude-dream-team/status"><img src="https://agentmods.dev/badge/commands/chrismckerracher/claude-dream-team/status.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.00027 | $0.00367 |
| Opus 5 | $0.00014 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
status 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 10d 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.
What it actually says
Dream Team Status Report
Generate a status report of the current Dream Team workflow.
Step 1: Gather Information
- Read the current task list using TaskList
- Check for any active team configuration
- Review recent task updates and agent messages
Step 2: Generate Report
Present the status in this format:
## Dream Team Status
### Active Workflow
[Epic/Bug/None] - [Name/Description]
### Team Members
| Agent | Status | Current Task |
|-------|--------|-------------|
| Team Lead | active | Coordinating |
| [Agent] | [active/idle] | [Task or "awaiting work"] |
### Task Progress
[X/Y] tasks completed
#### By Stage
- Pending: [count]
- In Progress: [count]
- In Review: [count]
- In QA: [count]
- Merge Ready: [count]
- Completed: [count]
### Review Pipeline
| Task | Stage | Assignee | Cycles |
|------|-------|----------|--------|
| [Task] | [Stage] | [Agent] | [N] |
### Blockers
- [Any blocked tasks or waiting-on-user items]
### Recent Activity
- [Last 3-5 significant events]
Step 3: Highlight Issues
If any issues are detected, call them out:
- Tasks stuck in review for > 2 cycles
- Review queue backing up
- Agents that appear idle with work available
- Tasks blocked on user input
- Critical errors that need attention
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.
- 10d ago First seen · 64 lines · 27 tokens per session scan A 5109ce91b454
status is a command published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 367 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.