redteam-mindset

Structure red-team engagements with cross-technique validation and evidence capture.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sseshachala/Claude-BugHunter-archive --skill redteam-mindset-sseshachala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redteam-mindset
Source: https://github.com/sseshachala/Claude-BugHunter-archive/tree/main/skills/redteam-mindset
Command: npx skills add https://github.com/sseshachala/Claude-BugHunter-archive --skill redteam-mindset-sseshachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Mindset skill provides the discipline and guardrails needed to distinguish offensive testing from defensive WAPT, ensuring testers maintain rigorous process, avoid premature conclusions, and relentlessly pursue validation across multiple techniques and targets.

Core Features & Use Cases

  • Provides a structured, repeatable cognitive framework for red-team operators.
  • Defines when to push for deeper testing, how to chase blockers, and how to avoid common anti-patterns.
  • Supports cross-application and sister-app pattern recognition, multi-technique validation, and real-time IR observations.

Quick Start

Load this mindset at the start of every red-team engagement and reapply it whenever you feel stuck or consider stopping.

Frequently Asked Questions about redteam-mindset

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

FAQPage Schema
How do I maintain discipline during a red-team engagement to avoid premature conclusions?

Maintain red-team engagement discipline by applying a structured cognitive framework that enforces cross-technique validation, cadence governance, and detailed evidence capture to prevent premature conclusions. This framework provides guardrails to push for deeper testing and relentlessly pursue validation across targets.

What is the difference between offensive security testing and defensive WAPT?

Offensive security testing differs from defensive WAPT by requiring rigorous process guardrails for adversary emulation. This mindset ensures testers avoid defensive anti-patterns and maintain methodical pursuit of multi-technique validation across external red-team scenarios.

How do I validate findings across multiple applications during adversary emulation?

Validate findings across multiple applications during adversary emulation by applying cross-technique validation and recognizing sister-app patterns. This framework supports real-time IR observations and ensures evidence capture across multi-app environments during active testing.

When should I apply a red-team mindset framework during an engagement?

Apply a red-team mindset framework during pre-engagement planning, active testing, and post-engagement review. Reload this cognitive framework whenever you feel stuck, encounter blockers, or consider stopping the engagement to ensure methodical discipline.

Does this red-team engagement framework support multi-app environments?

Yes, this red-team engagement framework supports multi-app environments by defining cross-application and sister-app pattern recognition. It applies cross-technique validation and real-time IR observations across external red-team and adversary-emulation scenarios on multiple targets.

What are common anti-patterns in red-team testing and how do I avoid them?

Common anti-patterns in red-team testing include premature conclusions, abandoning blockers, and skipping validation. Avoid them by applying engagement cadence governance, cross-technique validation, and detailed evidence capture throughout pre-engagement, active testing, and post-engagement review phases.