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/plugins/chrismckerracher/claude-dream-team/dream-team-plugin)<a href="https://agentmods.dev/plugins/chrismckerracher/claude-dream-team/dream-team-plugin"><img src="https://agentmods.dev/badge/plugins/chrismckerracher/claude-dream-team/dream-team-plugin/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/plugins/chrismckerracher/claude-dream-team/dream-team-plugin"><img src="https://agentmods.dev/badge/plugins/chrismckerracher/claude-dream-team/dream-team-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dream-team 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 8d 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.
This is a copy
91% identical to dream-team — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "dream-team",
"version": "1.0.5",
"description": "Multi-agent orchestration system for software development. Coordinates specialized agents (Team Lead, Architect, Product, QA, Code Review, Coding, UI/UX Designer) through structured Epic, Bug Discovery, and Continuous Improvement workflows with spelunk-based code exploration, git worktree isolation, and dtq-powered review queue.",
"author": {
"name": "Chris McKerracher",
"url": "https://github.com/ChrisMckerracher"
},
"repository": "https://github.com/ChrisMckerracher/claude-dream-team",
"license": "MIT",
"keywords": [
"multi-agent",
"orchestration",
"team",
"code-review",
"qa",
"architect",
"product",
"ui-ux",
"spelunking",
"worktree",
"epic",
"bug-discovery",
"dtq",
"review-queue"
]
}
What it installs
The manifest is a name and a version. 11 skills, 3 hooks travel with it, and installing the plugin installs all of them — 477 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill Review Queue Management A 50 tokens
- Skill Git Worktree Management A 38 tokens
- Skill Spelunking - Codebase Exploration A 52 tokens
- Skill Product Management A 41 tokens
- Skill Quality Assurance A 45 tokens
- Skill Team Lead Orchestration A 45 tokens
- Skill UI/UX Design A 40 tokens
- Skill Architecture Design A 40 tokens
- Skill Code Review A 36 tokens
- Skill Implementation & TDD A 44 tokens
- Skill Laws of UX Reference A 46 tokens
- Hook PreToolUse A not measured
- Hook PostToolUse A not measured
- Hook SessionStart A not measured
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 28 lines scan A 4d40222d72c2
dream-team is a plugin published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 91% identical to dream-team, differing in 8 lines, and is treated as a copy.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills-only: owns folder layout and templates; runs the Obsidian CLI directly via the official obsidian-cli skill.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.
product-management
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.