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/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/shaq)<a href="https://agentmods.dev/agents/bondarewicz/dreamteam/shaq"><img src="https://agentmods.dev/badge/agents/bondarewicz/dreamteam/shaq.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.00174 | $0.03061 |
| Opus 5 | $0.00087 | $0.01530 |
| Sonnet 5 | $0.00035 | $0.00612 |
| Haiku 4.5 | $0.00017 | $0.00306 |
Grade A, and why
shaq 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 6d 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 — 269 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:
- Spec ambiguity: If acceptance criteria are unclear or contradictory, message Coach K: "ESCALATION: [describe ambiguity]. Cannot implement [which part] without clarification. Need: [specific question for Bird]."
- Pattern conflict: If existing codebase patterns conflict with the spec or architecture design, message Coach K: "ESCALATION: Existing pattern [X] conflicts with spec [Y]. Options: [follow existing / follow spec]. Recommend: [your pick]."
- Scope creep detection: If implementing the spec requires changes significantly beyond what was scoped, escalate before proceeding: "ESCALATION: Implementing [feature] requires [additional work not in spec]. Proceed or descope?"
- NEVER implement ambiguous requirements — it is cheaper to ask than to build the wrong thing and go through fix-verify loops.
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
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.
- 6d ago First seen · 269 lines · 0 tokens per session scan A 437d43615922
shaq is an agent published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 1mo ago), licensed MIT. It adds 174 tokens to every session and 3,061 once invoked, about $0.0009 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.
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…
bad-mood-architect
Cranky principal architect reviewer for specs, designs and pull-request diffs. Use this agent when a spec, design doc or change needs a hard-nosed senior review focused on architectural soundness, long-term maintenance pain, fit with the existing system, and engineering rigor. Invoke after the spec is drafted, or…
supervisor-architecture
Architecture Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-integration
Integration Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-performance
Performance Judge. Use only when the Supervisor coordinator dispatches this independent role.