red-team-adversarial

Name: red-team-adversarial
Availability: InStock
Author: kbwen

Analyze code changes for exploitable weaknesses and generate attack surface assessments.

121|29|Updated Apr 12, 2026

Search Tags:#code-review #red-team #security-review #attack-surface #dependency-risk #adversarial-testing

Ready to run

npx skills add https://github.com/KbWen/agentic-os --skill red-team-adversarial

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: red-team-adversarial
Source: https://github.com/KbWen/agentic-os/tree/main/.agents/skills/red-team-adversarial
Command: npx skills add https://github.com/KbWen/agentic-os --skill red-team-adversarial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial thinking is applied to code changes to surface exploitable weaknesses that standard checks may miss.

Core Features & Use Cases

Auto-triggers during /review and /test based on task classification to run Red Team analyses.
Supports Lite Red Team, Full Red Team, and Beast Mode to cover quick checks and comprehensive assessments.
Provides attack surface analysis, boundary testing, authorization bypass attempts, dependency chain checks, and resilience testing.

Quick Start

Trigger a full Red Team analysis on the current change set during the next review or test.

Frequently Asked Questions about red-team-adversarial

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

FAQPage Schema

How do I automate adversarial security testing for code changes?▼

Adversarial security testing is automated by applying red team analysis during code reviews to surface exploitable weaknesses like boundary issues and authorization bypasses. The system auto-triggers based on task classification to run targeted attack surface assessments.

What is the difference between Lite Red Team and Full Red Team modes?▼

Lite Red Team provides quick security checks while Full Red Team executes comprehensive attack surface analyses, dependency chain checks, and resilience testing. You can select the appropriate auto-trigger mode based on the depth required for your code changes.

How do I run an attack surface analysis on my current code change set?▼

Attack surface analysis is executed by triggering a full Red Team analysis during your next code review or test. This automatically classifies the task and generates assessments for exploitable boundaries, authorization bypasses, and dependency risks.

When do I need adversarial testing instead of standard security reviews?▼

Adversarial testing is needed when standard security reviews may miss exploitable weaknesses in your code changes. It applies adversarial thinking to surface hidden boundary issues, dependency chain vulnerabilities, and authorization bypass attempts during automated reviews.

Can I use red team testing for dependency risk and boundary testing assessments?▼

Red team testing supports both dependency risk and boundary testing assessments. It evaluates dependency chain checks and performs boundary testing to identify exploitable weaknesses and enforce gate decisions based on prescribed security findings.