red-team
This skill should be used when the user asks to "plan a red team engagement", "scope a penetration test", "design a security assessment methodology", "create rules of engagement", or "plan an adversary simulation".
Install / Use
npx skills add borghei/Claude-Skills --skill red-teamInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of red-team
red-team scores 84/100 on our quality scale, 865th of 1,096 Security skills we index.
Its SKILL.md is 3.5 KB long, well organised into 15 sections with 1 code example: a solid amount of guidance for an agent.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so red-team is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
red-team compared with similar skills
All 4 of these similar skills score higher than red-team; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| red-team (this skill)by borghei | 84 | 817 | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
Frequently asked questions
- How do I install red-team?
- Run
npx skills add borghei/Claude-Skills --skill red-team. The install tabs above show the steps for each supported agent. - Which AI agents does red-team work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is red-team safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is red-team still maintained?
- The repository was last updated about 2 months ago, so red-team is actively maintained.
Skill content
View source on GitHubname: red-team description: > This skill should be used when the user asks to "plan a red team engagement", "scope a penetration test", "design a security assessment methodology", "create rules of engagement", or "plan an adversary simulation". license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: engineering domain: offensive-security updated: 2026-04-02 tags: [red-team, penetration-testing, security-assessment, adversary-simulation, engagement-planning]
Red Team
Category: Engineering Domain: Offensive Security
Overview
The Red Team skill provides tools for planning and scoping security engagements. It helps define rules of engagement, select methodologies, scope targets, plan attack phases, and generate engagement documentation.
Clarify First
Before planning the engagement, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Authorization & ROE owner — who has signed off and the escalation contacts (no engagement plan without confirmed authorization)
- [ ] In-scope targets & boundaries — the exact assets in and explicitly out of bounds (drives scope and
--target) - [ ] Engagement type — red-team / pentest / purple / bug-bounty (sets stealth, methodology, and
--type) - [ ] Compliance framework — e.g. pci-dss (maps test cases to controls via
--compliance)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
# Plan a red team engagement
python scripts/engagement_planner.py --type red-team --target "web application" --duration 2w
# Plan a penetration test
python scripts/engagement_planner.py --type pentest --target "api,network" --duration 1w --compliance pci-dss
# Generate rules of engagement document
python scripts/engagement_planner.py --type red-team --target "full-org" --output engagement_plan.json --format json
Tools Overview
| Tool | Purpose | Key Flags |
|------|---------|-----------|
| engagement_planner.py | Plan red team engagements with scope, rules, and methodology | --type, --target, --duration, --compliance |
engagement_planner.py
Generates comprehensive engagement plans including:
- Scope definition and boundaries
- Rules of engagement (ROE)
- Methodology selection (MITRE ATT&CK, OWASP, PTES, etc.)
- Phase breakdown with timelines
- Communication and escalation procedures
- Deliverables checklist
Workflows
Full Red Team Engagement
- Define engagement objectives and scope with
engagement_planner.py - Review generated rules of engagement with stakeholders
- Get formal sign-off on scope and ROE
- Execute phases per the plan timeline
- Document findings throughout
- Deliver final report
Compliance-Driven Pentest
- Run planner with
--complianceflag for framework-specific requirements - Map test cases to compliance controls
- Execute against compliance-specific checklist
- Generate evidence for auditors
Reference Documentation
- Red Team Methodology - Frameworks, attack phases, and engagement standards
Common Patterns
Engagement Types
- Red Team: Full adversary simulation, stealth required, tests detection/response
- Penetration Test: Authorized vulnerability exploitation, known to defenders
- Purple Team: Collaborative attack/defense, real-time knowledge sharing
- Bug Bounty Triage: Structured vulnerability validation from external reports
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
