An agent for checking whether a change is likely to keep working after it is integrated. It focuses on stability, integration testing, and operational readiness.

Use it to assess integration risks, test coverage, monitoring gaps, and whether a change is ready to operate reliably.

It helps expose failures that may not appear in a narrow code review, especially at boundaries between systems.

pippen — Agent for Claude Code by bondarewicz

Install

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.

Clone the repo

git clone --depth 1 https://github.com/bondarewicz/dreamteam

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/bondarewicz/dreamteam/pippen.svg)](https://agentmods.dev/agents/bondarewicz/dreamteam/pippen)

Your own site

<a href="https://agentmods.dev/agents/bondarewicz/dreamteam/pippen"><img src="https://agentmods.dev/badge/agents/bondarewicz/dreamteam/pippen.svg" alt="Measured on agentmods" height="20"></a>

Per session 176 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,061 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00176	$0.03061
Opus 5	$0.00088	$0.01530
Sonnet 5	$0.00035	$0.00612
Haiku 4.5	$0.00018	$0.00306

Measured 7d ago against content hash b4aaa826eba2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

pippen 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.

agents/pippen.md · 266 lines

How it starts

The opening of the file, as written. The whole thing — 266 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 TaskGet on your task to read the blockedBy list
For EACH blocker, run TaskGet to 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:

Integration risk unclear: If you cannot determine blast radius without more system context, message Coach K: "ESCALATION: [component] interacts with [unknown system]. Need MJ to clarify integration boundary before I can assess risk."
Missing observability baseline: If the codebase lacks monitoring and you cannot assess regression, message Coach K: "ESCALATION: No baseline metrics for [area]. Cannot assess operational readiness. Recommend adding [specific observability] before shipping."
Infrastructure dependency: If the change requires infrastructure changes (new queues, config, secrets) not mentioned in the spec, escalate: "ESCALATION: Implementation requires [infrastructure change] not in spec. Verify with user before shipping."
NEVER approve operational readiness when you lack visibility — if you can't monitor it, it's not production-ready.

Pre-Review Gate (MANDATORY)

Before starting ANY review:

Identify which files you need to review (from task description or Shaq's message)
Use Glob to verify those files actually exist on disk
If files DO NOT exist: message Coach K saying "Blocked — files not yet written" and STOP
Do NOT review based on task descriptions or messages alone — you MUST read actual code files

Read the full file on GitHub · 266 lines

Changes

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 · 266 lines · 0 tokens per session scan A b4aaa826eba2

Subscribe to this mod's changes

pippen is an agent published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 1mo ago), licensed MIT. It adds 176 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.

Claude Code Multi-Agent Testing agent-orchestration agentic-workflow ai-agents claude-code-agents

test-architect

Use after the worktree is prepared to write all failing acceptance tests from the structure. Tests form the immutable scope fence for implementation. Operates inside the implement phase as a sub-step before the implementer runs.

bostonaholic/team · 46 tokens

ux-reviewer

Use when live application verification is needed after implementation. Boots the application, interacts with it as a user would, and evaluates the experience. For API-only projects, sends real HTTP requests. Example triggers — "verify the app works", "test the UI", "check the user experience", "smoke test the…

bostonaholic/team · 68 tokens

verifier

Use when comprehensive verification checks need to run before completion. Runs all available checks (format, lint, type check, build, tests) in speed order and produces an evidence-based report. Example triggers — "run all checks", "verify the build", "pre-flight checks", "does everything pass".

bostonaholic/team · 63 tokens

pippen