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/abossenbroek/abossenbroek-claude-pluginsWrote 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/commands/abossenbroek/abossenbroek-claude-plugins/pr-redteam-branch)<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/pr-redteam-branch"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/pr-redteam-branch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/pr-redteam-branch"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/pr-redteam-branch.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.01498 |
| Opus 5 | $0.00005 | $0.00749 |
| Sonnet 5 | $0.00002 | $0.00300 |
| Haiku 4.5 | $0.00001 | $0.00150 |
Grade A, and why
pr-redteam-branch 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 10d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/redteam-pr:branch Command
Adversarial red team analysis of branch comparison for PR review.
Usage
/redteam-pr:branch <branch_spec> [mode]
Arguments
branch_spec (required):
- Branch comparison specification
- Format:
base...featureorbase..feature - Example:
/redteam-pr:branch main...feature-branch
mode (optional):
quick- Fast 2-3 vector analysis, skip groundingstandard- Balanced 5-6 vectors with basic grounding (default)deep- All categories + meta-analysis with full groundingfocus:[category]- Deep dive on specific category (e.g.,focus:reasoning-flaws)
Instructions
You are the MINIMAL entry point for PR red team analysis of branch comparisons. Your ONLY job is to:
- Execute git operations to compare branches
- Check PAL MCP availability (optional enhancement)
- Extract diff metadata, commit context, and build structured snapshot
- Launch the pr-analysis-coordinator agent with the snapshot
- Return the coordinator's output directly to the user
Step 1: Execute Git Operations
Use the Bash tool to get branch comparison data:
# Get file statistics for branch comparison
git diff <branch_spec> --numstat
# Get unified diff with 3 lines of context
git diff <branch_spec> -U3
# Get commit log for context
git log --oneline <branch_spec>
Replace <branch_spec> with the provided argument (e.g., main...feature).
If the branches do not exist or comparison fails, inform the user and exit.
Step 2: Check PAL Availability (Non-Blocking)
Launch the pal-availability-checker agent to detect if PAL MCP is available:
Task: Launch pal-availability-checker agent
Agent: agents/pal-availability-checker.md
Prompt: Check if PAL MCP is available and list models
Parse the YAML result and include pal_available: true/false in the snapshot.
This step is NON-BLOCKING - continue regardless of result. PAL is optional.
Step 3: Parse Mode
Determine mode from command arguments:
- Default mode:
standard
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.
- 10d ago First seen · 197 lines · 9 tokens per session scan A ddba3fe3875d
pr-redteam-branch is a command published in the GitHub repository abossenbroek/abossenbroek-claude-plugins (2 stars, last pushed 4mo ago), licensed BSD-3-Clause. It adds 9 tokens to every session and 1,498 once invoked, about $0.0000 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.