redteam-mindset

Enforces red-team operator discipline and anti-throttling rules during authorized offensive engagements.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill redteam-mindset-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redteam-mindset
Source: https://github.com/dbx0/skills/tree/main/skills/methodology/mindset/redteam-mindset
Command: npx skills add https://github.com/dbx0/skills --skill redteam-mindset-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operators on authorized red-team engagements frequently self-throttle: stopping at the first 403, retracting valid findings after one failed recheck, skipping sister applications, or treating blockers like WAFs and captchas as stop signs. This Skill corrects those conservative defaults so the engagement actually achieves its "gain access, prove impact" objective instead of degrading into a shallow WAPT-style scan. ## Core Features & Use Cases - Self-Throttling Detection: Lists 10+ explicit anti-patterns (mid-loop permission re-asks, single-probe testing, skill-gap-as-stop-condition) to flag and correct immediately. - Per-Host Completion Cadence: Defines a concrete checklist of what a finished host looks like — path probing, robots.txt/sitemap mining, JS bundle secret greping, full SQLi and auth-bypass class sweeps per parameter. - Blocker Decision Trees: Provides escalation paths for captchas, WAFs, rate limits, and slow timing-based exfiltration instead of declaring "not feasible". - Use Case: At the start of an authorized external red-team engagement, load this Skill to set scope discipline (access-yielding bugs over WAPT-class bugs), then consult it whenever stuck or tempted to stop, and use its pre/during/post-engagement checklists to validate completeness. ## Quick Start Load the redteam-mindset skill at the start of this authorized red-team engagement and use its checklists to decide whether each host is truly finished.

Frequently Asked Questions about redteam-mindset

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

FAQPage Schema
How do I avoid stopping too early on a red-team engagement?

Use the per-host completion cadence: probe top paths, read robots.txt and sitemap entries, grep JS bundles for secrets, and run full SQLi and auth-bypass class sweeps per parameter. A host is not finished until every test class has run on every live surface.

What is the difference between red-team scope and WAPT scope?

Red-team scope prioritizes access-yielding bugs like SQLi, RCE, SSRF, auth bypass, and hardcoded credentials. WAPT-class issues like IDOR, CSRF, reflected XSS, and missing headers are noted briefly but not pursued, since they do not yield sessions or footholds.

Should I retract a finding when the recheck fails?

No. Preserve the original PoC artifacts, then investigate the delta: diff response bodies, headers, and timing to identify what mitigation was deployed. A mid-engagement patch is itself a positive finding about the client's incident response capability.

When is this skill not appropriate to use?

Do not use it for bug bounty programs, WAPT or PCI-style assessments, or pure compliance audits, since those have different scope rules and stop conditions. It is designed specifically for authorized red-team and adversary-emulation engagements.

How do I bypass captchas and WAFs during authorized testing?

Follow the decision trees: for captchas try field omission, replay, OCR preprocessing, then paid solving services; for WAFs try slower pacing, encoding, alternate injection contexts, verb and content-type changes, and direct origin probing.