Skip to content
Back to skills

Red Team Review

ASecurity

(Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved.

  • 7 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 2, 2026
ai-agentspythonbashbackendsecurity

Works with

  • cli

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add richfrem/agent-plugins-skills --skill red-team-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Red Team Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Red Team Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/richfrem-red-team-review-agent-plugins-skills/badge)](https://www.skillsdirectory.com/skills/richfrem-red-team-review-agent-plugins-skills)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: red-team-review
plugin: agent-orchestration
description: "(Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved."
allowed-tools: Bash, Read, Write
---

# Red Team Review (red-team-review)

Orchestrated adversarial review loop pairing iterative plan/code generation with independent critique personas (Architecture Skeptic, Security Auditor, TDD Contract Reviewer) until an "Approved" verdict is earned.

## Contents
- [Critical Constraints](#critical-constraints)
- [Dependencies](#dependencies)
- [Quick start](#quick-start)
- [Workflow](#workflow)
- [Verification](#verification)
- [References](#references)

## Critical Constraints
1. **Fan-Out Trio Invariant**: Multi-persona reviews must dispatch to all 3 Graph Planning roles: Architecture Skeptic (`architect-review`), Security / Edge-Case Auditor (`security-auditor`), and TDD Contract Reviewer (`tdd-contract-reviewer`).
2. **Directory Isolation**: Save review packets and critique outputs to isolated directories (e.g. `.history/review-iteration-1/`) so baseline artifacts are never destructively overwritten.
3. **Convergence Limit**: If 2-3 rounds pass without approval, stop looping and escalate outstanding disagreements to human/orchestrator tie-breaker.
4. **Non-Interactive Input Redirection**: Always append `< /dev/null` to headless CLI commands to prevent `SIGTTIN` hangs.

## Dependencies
- **`context-bundler`** (dev-utils) — Required for creating review packets in Multi-Persona Fan-Out Mode
- **Adversarial personas**: `architect-review`, `security-auditor`, `tdd-contract-reviewer` in `cli-agents`

## Quick start

```bash
# Bundle context using the context-bundler skill in dev-utils
python3 plugins/dev-utils/scripts/bundle_context.py --manifest manifest.json --out temp/review/
```

## Workflow

1. **Research & Packet Generation**: Draft `red-team-prompt.md`, prepare `manifest.json`, and run `context-bundler` in Multi-Persona Fan-Out Mode to generate persona packets.
2. **Select Backend**: Interactively confirm CLI backend (`agy`, `claude`, `copilot`, `codex`) and model tier with user.
3. **Parallel Dispatch**: Dispatch review bundles in parallel to designated persona reviewers.
4. **Synthesize Feedback**: Capture verdicts. If "More Research Needed", iterate with targeted questions. If consensus is reached, advance.
5. **Handoff**: On approval, terminate review loop and pass approved artifacts back to parent orchestrator.

## Verification

```bash
# Execute project unit tests to verify no regressions were introduced
pytest tests/ -k "not test_health_check_signing_status"
```

## References
- [acceptance-criteria.md](references/acceptance-criteria.md) — Review criteria, persona responsibilities, and approval definitions.
- [fallback-tree.md](references/fallback-tree.md) — Deadlock breaking and escalation protocol when reviewers disagree.

Files in this skill

  • SKILL.md5.2 KB
  • acceptance-criteria.md743 B
  • assets/resources/red_team_review_loop.mmd52 B
  • evals/evals.json830 B
  • evals/results.tsv301 B
  • fallback-tree.md1.3 KB
  • references/acceptance-criteria.md42 B
  • references/fallback-tree.md36 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.