←Leaderboard/Security/Claude-Red
Last commit on September 13, 2026·Created on March 4, 2026

SnailSploit/Claude-Red

“Test networks and applications for security weaknesses.”
Combined rank
#69
across all skills
In Security
#4
category rank
Stars
10.4k
+6.3% in last 7d
Forks
1.4k
+5.4% in last 7d
Watchers
67
+4.7% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

Claude-Red provides red team operators with structured guidance for internal network engagements. It focuses on the technical execution of reconnaissance, credential abuse, and lateral movement within Active Directory forests.

The skill set covers the progression from initial access to full domain compromise, detailing specific techniques for ADCS abuse and evasion of modern identity defense systems.

WHO IT'S FOR
Red team operators
executing internal network and AD engagements
Penetration testers
testing REST, gRPC, and WebSocket APIs
AI security researchers
red-teaming LLMs and AI systems
Offensive security engineers
automating attack vectors using AI assistants
Categories
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

See the repository for installation instructions.

Open repository instructions ↗

Give it something to do.

Suggested first task

Draft a scoped SQL-injection test plan

Uses offensive-sqli

  • Authorized staging endpoint URL
  • Sanitized HTTP or API request example
  • Explicitly in-scope parameters and input vectors
  • Known database or framework details, if available

Make sure offensive-sqli is installed in your agent before trying this task.

Use the offensive-sqli skill to draft a compact, non-destructive SQL-injection testing plan for an authorized staging endpoint. Map the supplied request's URL parameters, body fields, cookies, headers, API filters, and other database-facing inputs; then identify suitable basic, error-based, and boolean/time-based detection checks and the evidence to record. Do not execute requests. Inputs: the staging endpoint URL, a sanitized request example, the explicitly in-scope parameters, and any known database or framework details.
Suggested first task

Triage Bluetooth Classic service exposure

Uses offensive-bluetooth-classic

  • Authorized Bluetooth Classic device inventory
  • Device model and firmware information
  • Sanitized SDP service records
  • Engagement scope and permitted validation boundaries

Make sure offensive-bluetooth-classic is installed in your agent before trying this task.

Use the offensive-bluetooth-classic skill to review an authorized device inventory and sanitized SDP service records. Produce a short exposure table listing each device, advertised profile, likely authentication boundary, legacy attack relevance, and the safest next validation step. Do not connect to or modify any device. Inputs: device models and firmware versions, Bluetooth addresses replaced with placeholders if needed, and SDP service records.
Suggested first task

Assess KRACK and FragAttacks applicability

Uses offensive-krack-fragattacks

  • Authorized Wi-Fi client inventory
  • Client model and vendor
  • Operating-system or firmware version
  • Patch date or patch status
  • Deployment context, such as embedded, IoT, industrial, or modern desktop/mobile

Make sure offensive-krack-fragattacks is installed in your agent before trying this task.

Use the offensive-krack-fragattacks skill to triage an authorized client-device inventory without running an attack. For each client, estimate whether KRACK or FragAttacks testing is likely relevant from its device type, operating system, firmware, and patch date; identify the applicable attack family and CVEs to investigate; and list the evidence needed before controlled testing. Inputs: client models, operating-system or firmware versions, patch dates, and deployment context.