redteam-mindset

Guide offensive red-team testing with disciplined decision-making and evidence capture.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined, repeatable red-team mindset to guide offensive testing from start to finish, ensuring consistent decision-making and avoiding premature stop conditions. It emphasizes distinguishing adversary emulation from defensive WAPT, preventing scope creep and missed findings.

Core Features & Use Cases

  • Mindset corrections that keep engagements moving, reduce stalls, and ensure rigorous coverage across targets.
  • Real-engagement cadence guidance, including top surface probing, sister-app sweeps, and multi-technique validation to produce credible findings.
  • Evidence hygiene and reporting alignment, enabling structured journaling and artifact capture for durable deliverables.

Quick Start

Load the redteam-mindset skill at the START of a red-team engagement to activate its disciplined playbook.

Frequently Asked Questions about redteam-mindset

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

FAQPage Schema
What is a red-team mindset and how does it guide adversary emulation engagements?

A red-team mindset provides a disciplined, repeatable framework to guide offensive testing from start to finish, ensuring consistent decision-making during adversary emulation and avoiding premature stop conditions. It emphasizes distinguishing offensive emulation from defensive WAPT to prevent scope creep.

How do I maintain engagement cadence and avoid premature stop conditions during red-team testing?

To maintain engagement cadence, apply mindset corrections that keep testing moving across targets by performing top surface probing, sister-app sweeps, and multi-technique validation. This scalable, cross-surface approach uses 2+ techniques to ensure rigorous coverage and produce credible findings.

How do I capture evidence and structure reporting for authorized red-team engagements?

Capture evidence for authorized red-team engagements by practicing evidence hygiene and reporting alignment. This involves structured journaling and artifact capture throughout the testing process to support durable deliverables and credible impact findings.

Can I use this red-team mindset for external engagement scenarios and adversary-emulation exercises?

Yes, you can use this red-team mindset for authorized red-team engagements, adversary-emulation exercises, and external engagement scenarios. It is specifically designed for contexts where proving impact is the primary objective across multiple target surfaces.

When should I not use an adversary-emulation mindset instead of defensive web application penetration testing?

You should not use an adversary-emulation mindset when your objective is defensive WAPT rather than proving impact. The red-team mindset explicitly distinguishes adversary emulation from defensive WAPT to prevent scope creep and missed findings during offensive operations.

What's the best way to validate credible findings during cross-surface offensive testing?

The best way to validate credible findings during cross-surface offensive testing is applying 2+ techniques and performing sister-app sweeps. This multi-technique validation ensures rigorous coverage and prevents premature stop conditions during adversary emulation.