redteam-mindset

Enforce disciplined thinking and decision-making across red-team engagement stages.

Updated May 31, 2026

Search Tags:#validation #mindset #red-team #cadence #security-engagement #evidence-hygiene

Ready to run

npx skills add https://github.com/grivera82/pi-bughunter --skill redteam-mindset-grivera82

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: redteam-mindset
Source: https://github.com/grivera82/pi-bughunter/tree/main/skills/redteam-mindset
Command: npx skills add https://github.com/grivera82/pi-bughunter --skill redteam-mindset-grivera82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Red-team operators often lose focus on disciplined decision-making, leading to scope creep, overlooked blockers, and inconsistent results. This skill enforces a structured mindset across engagement stages to keep testing rigorous and defensible.

Core Features & Use Cases

9 mindset corrections to reduce common red-team pitfalls (authorization gating, marker discipline, data capture, evidence hygiene, etc.)
Real-engagement cadence guidance including per-host and cross-app sweeps
Cross-technique validation to strengthen findings and evidence quality

Quick Start

Apply the redteam-mindset framework to a live engagement, implementing the 9 corrections and the real-engagement cadence.

Frequently Asked Questions about redteam-mindset

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

FAQPage Schema

How do I maintain a disciplined red-team mindset throughout a security engagement?▼

Maintain a disciplined red-team mindset by applying nine structured mindset corrections across initial scoping, execution, and reporting. This framework enforces consistent decision-making and structured evidence capture to ensure defensible findings.

What is multi-technique validation in red-team engagements?▼

Multi-technique validation in red-team engagements is the practice of cross-checking findings using different methods to strengthen evidence quality. It ensures reproducible, auditable results by verifying scope and markers before reporting.

How do I prevent scope creep and overlooked blockers during red-team execution?▼

Prevent scope creep during red-team execution by enforcing authorization gating, marker discipline, and structured data capture. Applying real-engagement cadences like per-host sweeps keeps testing focused and identifies blockers early.

Can I use this red-team mindset framework for cross-application testing cadences?▼

Yes, you can apply this red-team mindset framework to cross-application testing. It provides real-engagement cadence guidance including cross-app sweeps to ensure consistent evidence hygiene and reproducible results across your defined scope.

How do I enforce evidence hygiene when capturing red-team engagement data?▼

Enforce evidence hygiene by applying structured data capture rules throughout the engagement lifecycle. The framework requires multi-technique validation and strict marker discipline to produce auditable, defensible findings.

When should I not use a structured red-team mindset approach?▼

You should not use a structured red-team mindset approach when your security engagement lacks a clearly defined scope. The framework requires strict authorization gating and structured evidence capture to produce consistent, defensible results.