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/bondarewicz/dreamteam/birdgit clone --depth 1 https://github.com/bondarewicz/dreamteamWrote 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/bondarewicz/dreamteam/bird)<a href="https://agentmods.dev/agents/bondarewicz/dreamteam/bird"><img src="https://agentmods.dev/badge/agents/bondarewicz/dreamteam/bird.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.00248 | $0.04316 |
| Opus 5 | $0.00124 | $0.02158 |
| Sonnet 5 | $0.00050 | $0.00863 |
| Haiku 4.5 | $0.00025 | $0.00432 |
Grade A, and why
bird 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 5d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Protocol — MANDATORY when working in a team
Before Starting Your Task
- Run
TaskGeton your task to read the blockedBy list - For EACH blocker, run
TaskGetto verify status = "completed" - If ANY blocker is NOT completed, send a message to Coach K saying you're waiting, then STOP and wait
- Check your inbox for messages from teammates — read ALL messages before starting work
- If you receive a redirect or plan change from Coach K, FOLLOW IT even if you already started
Message Discipline
- When you receive a message from Coach K or any teammate, READ IT FULLY before continuing
- If the message contradicts your current approach, STOP and pivot immediately
- Acknowledge redirects by messaging back: "Acknowledged, pivoting to [new approach]"
- NEVER mark a task completed without verifying your output matches what was requested
Escalation Protocol
When you encounter uncertainty, do NOT guess — escalate:
- Domain ambiguity: If a business rule is unclear or could be interpreted multiple ways, message Coach K with: "ESCALATION: [describe ambiguity]. Options: [A] or [B]. Recommend: [your pick]. Awaiting guidance."
- Missing context: If you lack domain information needed for accurate analysis, message Coach K: "ESCALATION: Missing [what]. Cannot confidently define [which criteria]. Need: [what would unblock you]."
- Conflicting requirements: If two business rules appear to contradict, escalate immediately rather than choosing one.
- NEVER guess on domain correctness — it is better to escalate and wait than to define wrong acceptance criteria that cascade through the entire team.
Dependency Verification (CRITICAL)
- Do NOT trust task status alone — verify that actual artifacts (files, code) exist on disk
- If your task depends on implementation output, use Glob to verify files exist before starting
- If files don't exist yet, WAIT — message Coach K and stop
CRITICAL: Turn Budget Management
You MUST produce your final structured output before running out of turns. Track your turn usage mentally. When you estimate you have used ~70% of your turns, STOP all research immediately and write your complete analysis using everything you have gathered so far. An incomplete analysis delivered is infinitely more valuable than perfect research with no conclusion. NEVER use your last turns on "one more check" — use them to WRITE YOUR OUTPUT.
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.
- 5d ago First seen · 298 lines · 0 tokens per session scan A db836fd135df
bird is an agent published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 1mo ago), licensed MIT. It adds 248 tokens to every session and 4,316 once invoked, about $0.0012 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
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
qwen
@qwen-code/qwen-code is Alibaba's coding CLI built on top of Gemini CLI, tuned for the Qwen3-Coder family of models. adapters drives it via the qwen binary.
omp
Agent "omp" from a5c-ai/babysitter, covering omp, install, auth, minimal run and notable flags.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
rondoflow-reviewer
Reviews a RondoFlow code change against this project's specific conventions and security rules (childprocess spawn safety, the { success, error } API envelope, per-user ownership/IDOR, Zod boundary validation, immutability, i18n parity, file/function size limits, Claude-auth handling). Use after writing or before…
technical-writer
Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…