Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Ratler/dream-team/plugin install 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/skills/ratler/dream-team/spec-team)<a href="https://agentmods.dev/skills/ratler/dream-team/spec-team"><img src="https://agentmods.dev/badge/skills/ratler/dream-team/spec-team.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.00034 | $0.01384 |
| Opus 5 | $0.00017 | $0.00692 |
| Sonnet 5 | $0.00007 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
spec-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 7d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Team Spec
Convert the brainstorming conversation into a formal spec file for team execution — separate Claude Code instances that work in parallel and communicate via shared task list and mailbox.
Prerequisites: This skill assumes /dream-team:plan has already been run in this session. If the conversation has no brainstorming context (no discussed requirements, no confirmed approach, no validated task breakdown), stop and tell the user: "No brainstorming context found. Run /dream-team:plan <prompt> first to explore requirements and design."
Requires: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS enabled in settings.
What To Do
- Read the spec template at
${CLAUDE_PLUGIN_ROOT}/templates/spec-template.mdand the spec writing guide at${CLAUDE_PLUGIN_ROOT}/templates/spec-writing-guide.md. Follow the guide's filename format, ambiguity elimination, and git instructions. - Read the available agent definitions at
${CLAUDE_PLUGIN_ROOT}/agents/*.md. - Summarize the agreed plan from the conversation — confirm with the user before writing.
- Write the spec, filling in all sections from the brainstorming context.
- Set frontmatter
mode: teamandspec-version: 1. - Set frontmatter
playwright: trueif the brainstorming decided to use Playwright MCP, otherwiseplaywright: false. - Set frontmatter
frontend-design: trueif the brainstorming discussed frontend/UI work and design direction, otherwisefrontend-design: false. - If
frontend-design: true, fill in the## Design Directionsection with the aesthetic style, stack, component libraries, and design notes from the brainstorming conversation. Auto-suggest component libraries based on the chosen stack if not explicitly discussed. - Design for MAXIMUM INDEPENDENCE between teammates — avoid assigning same-file edits to different agents.
- Set
plan_approval: truefor high-risk or architectural tasks. - Size tasks at 5-6 per agent role for optimal productivity.
- Include Team Configuration and Review Policy sections.
- Fill in the
## Cleanupsection with any teardown commands needed (stop servers, remove temp files). Use "N/A" if nothing to clean up. - Save to
specs/YYYY-MM-DD-<descriptive-kebab-case>.mdusing today's date.
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.
- 7d ago First seen · 86 lines · 34 tokens per session scan A 6b34f068e5df
spec-team is a skill published in the GitHub repository Ratler/dream-team (16 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,384 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…