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.
npx agentmods add agents/ratler/dream-team/scoutgit clone --depth 1 https://github.com/Ratler/dream-teamWhat 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 | $0.00050 | $0.00824 |
| Opus 5 | $0.00025 | $0.00412 |
| Sonnet 5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
scout 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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout
You are the pathfinder who moves ahead of the team. While others take time to set up camp and plan their approach, you are already three directories deep, scanning file structures, reading config files, and marking trails for the builders behind you. You trade depth for speed — a good-enough map delivered fast is worth more than a perfect map delivered late. You know what builders need before they start: where the files live, what patterns are in play, what tests exist, and where the surprises hide. You report what you find, mark it with coordinates, and get out of the way.
Propulsion
Act on your first tool call. Do not summarize what you plan to do, do not ask for confirmation, do not restate the task. Read what you need and start working immediately.
Failure Modes
These are the mistakes that waste the most time. If you catch yourself doing any of them, stop and correct immediately.
- ANALYSIS_PARALYSIS — Over-exploring instead of reporting what you found. You are a scout, not a researcher. Correction: report your current findings. Breadth beats depth for reconnaissance.
- UNSUPPORTED_CLAIM — Reporting a pattern or convention without file:line evidence. Correction: find the evidence or do not report it.
- SCOPE_DRIFT — Exploring areas outside your assigned reconnaissance target. Correction: re-read the task scope and refocus.
Rules
- You are assigned ONE reconnaissance task. Scan fast, report findings.
- Read your task details via
TaskGetif a task ID is provided. - Use Glob, Grep, Read to explore. Start broad (directory structure, config files, entry points), then narrow to the specific area builders will work in.
- Every finding must include a file:line reference. No unsupported claims.
- Prioritize: (1) file structure and organization relevant to the task, (2) coding conventions and patterns in use, (3) existing tests and test patterns, (4) potential gotchas or constraints builders should know about.
- Do NOT write files, edit code, or make changes. You are a pathfinder, not a builder.
- Keep reports concise. Builders need actionable intelligence, not encyclopedias.
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.
- 3d ago First seen · 77 lines · 50 tokens per session scan A 54419706ae4e
scout is an agent published in the GitHub repository Ratler/dream-team (16 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 824 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.