A command for adversarially examining a conversation, file, or recent code changes for weaknesses. Red-team analysis means deliberately looking for ways something could fail or be misused.

Running quick, standard, or deep reviews of a conversation, a specific file, or recent changes, with optional focus on one problem category.

It can expose flawed reasoning, overlooked risks, and problems that a normal review may miss.

redteam — Command for Claude Code by abossenbroek

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/abossenbroek/abossenbroek-claude-plugins

Made for: Claude Code.

Or install red-agent, the plugin that ships this one along with the rest of its 2 skills, 7 commands.

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/commands/abossenbroek/abossenbroek-claude-plugins/redteam/github.svg)](https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/redteam)

Your own site

<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/redteam"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/redteam/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/redteam"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/redteam.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 868 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.00013	$0.00868
Opus 5	$0.00006	$0.00434
Sonnet 5	$0.00003	$0.00174
Haiku 4.5	$0.00001	$0.00087

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

Security

Grade A, and why

redteam 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 9d 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.

red-agent/commands/redteam.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/redteam Command

Adversarial red team analysis of the current conversation or specified target.

Usage

/redteam [mode] [target]

Arguments

mode (optional):

quick - Fast 2-3 vector analysis, skip grounding
standard - Balanced 5-6 vectors with basic grounding (default)
deep - All categories + meta-analysis with full grounding
focus:[category] - Deep dive on specific category (e.g., focus:reasoning-flaws)

target (optional):

conversation - Current conversation context (default)
file:path - Analyze specific file
code - Analyze recent git changes

Instructions

You are the MINIMAL entry point for red team analysis. Your ONLY job is to:

Check PAL MCP availability (optional enhancement)
Parse the mode and target from arguments
Extract a structured context snapshot
Launch the red-team-coordinator agent with the snapshot
Return the coordinator's output directly to the user

Step 1: 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 2: Parse Arguments

Determine mode and target from the command arguments:

Default mode: standard
Default target: conversation

Step 3: Extract Context Snapshot

Create a YAML-formatted snapshot of the current session. DO NOT include raw conversation - structure it as data:

snapshot:
  mode: [parsed mode]
  target: [parsed target]
  pal_available: [true/false from Step 1]
  pal_models: [list of models if available, empty if not]

  conversational_arc:
    message_count: [count of messages in conversation]
    phases:
      - phase: "[phase name]"
        messages: [range]
        summary: "[what happened in this phase]"
    key_transitions:
      - from_msg: [number]
        to_msg: [number]
        note: "[what changed and why]"
    early_assumptions_carried_forward:
      - assumption: "[assumption text]"
        introduced_at: [message number]
        still_active: [true/false]

  claims:
    - id: C[N]
      text: "[factual claim made by assistant]"
      speaker: assistant
      confidence: [stated_as_fact|hedged|uncertain]
      message_num: [source message number]

  files_read:
    - path: [file path]
      summary: "[brief description of content/purpose]"

  tools_invoked:
    - tool: [tool name]
      command: "[command or action]"
      outcome: "[result summary]"

  decisions:
    - decision: "[decision made]"
      rationale: "[stated reason]"

  assumptions_explicit:
    - "[explicitly stated assumption]"

Read the full file on GitHub · 137 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.

9d ago First seen · 137 lines · 13 tokens per session scan A e00deb78044a

Subscribe to this mod's changes

redteam is a command published in the GitHub repository abossenbroek/abossenbroek-claude-plugins (2 stars, last pushed 4mo ago), licensed BSD-3-Clause. It adds 13 tokens to every session and 868 once invoked, about $0.0001 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.

Security

redteam

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/redteam Command

Usage

Arguments

Instructions

Step 1: Check PAL Availability (Non-Blocking)

Step 2: Parse Arguments

Step 3: Extract Context Snapshot

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement