red-team

Generates concrete adversarial inputs to break validation logic, parsers, and prompt pipelines.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill red-team-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: red-team
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/red-team
Command: npx skills add https://github.com/sumitake/agent-collab --skill red-team-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security boundaries, input validators, and prompt pipelines often ship with undiscovered bypasses because passive code review only looks for defects rather than actively attacking the control surface. This Skill tasks an independent verifier with generating exact adversarial inputs — payloads, malformed strings, injection prompts — designed to bypass, crash, or trigger misbehavior in a system you just built. ## Core Features & Use Cases - Adversarial Input Generation: Produces exact attack strings, payloads, and scenarios against a specified target with a defined threat model and success criterion (bypass, crash, or misbehavior). - Verifier Independence Contract: Enforces caller-verified reviewer lineage so the red-team pass comes from a model family distinct from both the primary and the artifact author. - Finding Verification Loop: Requires each claimed attack to be tested against the real system, categorized by attack class, scored by severity, and paired with concrete fix recommendations. - Use Case: After building a login rate-limiter, dispatch the verifier to generate inputs that desynchronize its per-IP counter via X-Forwarded-For spoofing, then test each claim locally before reporting. ## Quick Start Ask the agent to red-team the validation logic or prompt pipeline you just built and generate ten concrete adversarial inputs that bypass it.

Frequently Asked Questions about red-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I red-team input validation logic with an AI reviewer?▼

Provide the verifier with the exact specification and code, a threat model, and a success criterion such as bypass or crash. It returns concrete adversarial strings and payloads, which you must test against the real system before reporting.

What is the difference between red-teaming and code review?▼

Code review passively looks for defect classes in an artifact, while red-teaming actively generates specific attack inputs against a defined control surface. Use code review for general bug-finding and red-team when a concrete adversary exists.

When should I not run an adversarial red-team pass?▼

Skip it when the artifact is not a control surface, has no defined adversary, or was already red-teamed without changes. UI-only changes, draft emails, and brainstorm outputs produce no useful adversarial findings.

Does an empty adversarial findings list prove my system is secure?▼

No. An empty result is a failure-to-find, not a soundness guarantee. The verifier may not have explored all attack classes, so treat it as one productive sample rather than proof of security.

Why must red-team findings be tested before reporting?▼

Verifiers generate plausible inputs without ground-truth verification, so hallucinated attack vectors are common. Running each input against the real system or a faithful local reproduction filters out false claims before they reach the user.