Agent skill · Security

red-team

Use when planning or executing authorized red team engagements, attack path analysis, or offensive security simulations. Covers MITRE ATT&CK kill-chain planning, technique scoring, choke point identification, OPSEC risk assessment, and crown jewel targeting.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill red-team --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 15 KB
Bundled scripts: yes
Path: engineering-team/skills/red-team/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Red Team Red team engagement planning and attack path analysis skill for authorized offensive security simulations. This is NOT vulnerability scanning (see security-pen-testing) or incident response (see incident-response) — this is about structured adversary simulation to test detection, response, and control effectiveness. --- ## Table of Contents - [Overview](#overview) - [Engagement Planner Tool](#engagement-planner-tool) - [Kill-Chain Phase Methodology](#kill-chain-phase-methodology) - [Technique Scoring and Prioritization](#technique-scoring-and-prioritization) - [Choke Point Analysis](#choke-point-analysis) - [OPSEC Risk Assessment](#opsec-risk-assessment) - [Crown Jewel Targeting](#crown-jewel-targeting) - [Attack Path Methodology](#attack-path-methodology) - [Workflows](#workflows) - [Anti-Patterns](#anti-patterns) - [Cross-References](#cross-references) --- ## Overview ### What This Skill Does This skill provides the methodology and tooling for **red team engagement planning** — building structured attack plans from MITRE ATT&CK technique selection, access level, and crown jewel targets. It scores techniques by effort and detection risk, assembles kill-chain phases, ide

What's inside
Steps it walks through
  1. Table of Contents
  2. Overview
  3. What This Skill Does
  4. Distinction from Other Security Skills
  5. Authorization Requirement
  6. Engagement Planner Tool
  7. Access Level Definitions
  8. Exit Codes
  9. Kill-Chain Phase Methodology
  10. Kill-Chain Phase Order
  11. Phase Execution Principles
  12. Technique Scoring and Prioritization
  13. Effort Score Formula
  14. Technique Scoring Reference
Ships with 2 files
  • references/attack-path-methodology.md
  • scripts/engagement_planner.py
Commands it runs
Basic engagement plan — external access, specific techniques
python3 scripts/engagement_planner.py \
Internal network access with crown jewel targeting
Credentialed (assumed breach) scenario with scale
List all 29 supported MITRE ATT&CK techniques
python3 scripts/engagement_planner.py --list-techniques
Assumed breach — credentialed access starting position
Run across multiple access levels to compare path options
for level in external internal credentialed; do
echo "=== ${level} ==="
More from claude-skills
All skills →
About this skill
What does the red-team skill do?

Use when planning or executing authorized red team engagements, attack path analysis, or offensive security simulations. Covers MITRE ATT&CK kill-chain planning, technique scoring, choke point identification, OPSEC risk assessment, and crown jewel targeting.

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill red-team --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going