AI Slop Code RIsk Monitor

SnailSploit/Claude-Red

claude-red is a curated library of offensive security skills designed for the Claude skills system. Each skill is a structured SKILL.md file that primes Claude with expert-level methodology for a specific attack surface — from SQLi to shellcode, EDR evasion to exploit development.

4.8 Low pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for SnailSploit/Claude-Red, a Python project with 7,422 GitHub stars. SynthScan examined 97,843 lines of code across 92 source files, recording 414 pattern matches distributed across 13 syntactic categories. The legacy adjusted pattern signal is 4.8 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

4.8
Adjusted Signal
4.8
Raw Pattern Score
100%
Time Factor
2026-09-19
Last Push
7.4K
Stars
Python
Language
97.8K
Lines of Code
92
Files
414
Pattern Hits
2026-10-12
Scan Date
0.04
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 13.6/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 324 finding(s).

Hallucinated Dependency & Supply Chain Risk 1.9/100 · LOW

Are imports declared and package/API names verified? 10 finding(s).

Agent Over-Engineering Ratio 7.4/100 · LOW

Are wrappers, guards, and repeated structures necessary? 84 finding(s).

PR Review Velocity Impact 24.7/100 · LOW

Which changes need focused human review? 414 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 3HIGH 1MEDIUM 54LOW 356

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 414 distinct pattern matches across 13 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Structural Annotation Overuse177 hits · 182 pts
SeverityFileLineSnippetContext
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1865# Step 1: Generate a cyclic pattern (de Bruijn sequence)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1874# Step 2: Crash the program with the patternCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1878# Step 3: Analyze the crash in GDB/Pwndbg (use the correct crash file- cwd or proper location)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1884# Step 4: Find the offset using the pattern in RIPCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1893# Step 5: Verify control - overwrite RIP with a known valueCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2076# Step 1: Find where return address is storedCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2083# Step 2: Query all writes to return address locationCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2088# Step 3: Navigate to the corruption pointCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2091# Step 4: Examine the guilty instructionCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2096# Step 5: Check registers to see the overflow in actionCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2106# Step 1: Find and navigate to main()COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2114# Step 2: Examine argv (RDX = argv in Windows x64 calling convention)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2121# Step 3: View the malicious inputCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2127# Step 4: See how input reaches vulnerable functionCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2132# Step 5: Find all reads from the input buffer to trace data flowCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2142# Step 1: Enable PageHeap for reliable UAF detection (run as admin)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2145# Step 2: Record UAF crash with TTDCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2152# Step 3: Run to the crashCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md2159# Step 4: Analyze the crashCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md3021# Step 1: Check if crash is on object method callCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md3025# Step 2: Check the object pointerCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md3029# Step 3: Check heap state (requires PageHeap enabled)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md3033# Step 4: Back-trace with TTD (if available)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7071# Step 1: Record execution with crash input (test case 1 = stack overflow)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7075# Step 2: Decode the trace to see all branches takenCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7079# Step 3: Find the crash point - last branches before crashCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7090# Step 4: Convert to coverage for visualizationCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7094# Step 5: Compare with benign input (no crash - input fits in buffer)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7098# Step 6: Find unique crash path (code only hit during overflow)COMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7102# Step 7: Examine the unique addressesCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1980# Step 8: Use TTD to examine the crash pointCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1987# Step 9: Examine the corrupted stack before ret executesCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2172# Step 5: Find all heap frees and identify the one matching crash addressCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2181# Step 6: Get details on the free and navigate to itCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2193# Step 7: Navigate to use_after_free function entryCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2202# Step 8: Examine the freed memory at crash pointCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2217# Step 9: Don't forget to disable PageHeap after analysisCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md6427#### Step 1: Generate CASR ReportsCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md6457#### Step 2: Cluster Similar CrashesCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md6477#### Step 3: Prioritize by ExploitabilityCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md6497#### Step 4: Interactive Review with casr-cliCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md6510#### Step 5: Document FindingsCOMMENT
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7628# Step 1: Record the crashSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7631# Step 2: Replay and analyzeSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7639# Step 3: Use reverse-next to trace back through executionSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7648# Step 4: Set breakpoint and replay from start to catch corruption in actionSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7654# Step 5: Now buffer is in scope - examine stack layout and save return addressSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7665# Step 6: Break at strcpy call (avoids PLT resolution noise)STRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7670# Step 7: Set watchpoint on saved return address and continue into strcpySTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md7680# Step 8: Examine where we are - inside strcpy during the overflowSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md10449 # Step 1: MinimizeSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md10453 # Step 2: AnalyzeSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md10459 # Step 3: Generate PoCSTRING
LOW⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md10463 # Step 4: Test PoCSTRING
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md11730# Step 1: Generate CASR reports for vuln_rop crashesSTRING
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md11762# Step 2: Cluster crashesSTRING
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md11766# Step 3: Review clustersSTRING
LOW⚡…ills/exploit-dev/offensive-basic-exploitation/SKILL.md2143# Step 1: Disassemble the binarySTRING
LOW⚡…ills/exploit-dev/offensive-basic-exploitation/SKILL.md2146# Step 2: Search for 'ret' instructions (opcode: 0xc3)STRING
LOW⚡…ills/exploit-dev/offensive-basic-exploitation/SKILL.md2149# Step 3: Look backwards from each 'ret' for useful sequencesSTRING
117 more matches not shown…
Decorative Section Separators46 hits · 128 pts
SeverityFileLineSnippetContext
MEDIUM⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1395#───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUM⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1397#───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUM⚡Skills/exploit-dev/offensive-crash-analysis/SKILL.md1400#───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md1377#──────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ REGCOMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md4064# =================================================================COMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md4068# =================================================================COMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md5104#──────────────────────────────────────────────────────────────────────────────────────────────────────────────────[ REGCOMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md5122#───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md5125#───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md8371#=================================================================COMMENT
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md10516# ============================================================STRING
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md10518# ============================================================STRING
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md11110# ==================STRING
MEDIUMSkills/exploit-dev/offensive-crash-analysis/SKILL.md11119# ==================STRING
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md85# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md87# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md112# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md114# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md144# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md146# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md263# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md265# ============================================================COMMENT
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md1940# ============================================================STRING
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md1942# ============================================================STRING
MEDIUM…ills/exploit-dev/offensive-basic-exploitation/SKILL.md1955# ============================================================STRING
MEDIUM⚡…/infrastructure/offensive-windows-mitigations/SKILL.md1141# ----------------------------------------------------------------------------------------------------------------------COMMENT
MEDIUM…/infrastructure/offensive-windows-mitigations/SKILL.md1434# ---------------------------------------------COMMENT
MEDIUM…/infrastructure/offensive-windows-mitigations/SKILL.md1443# ------------------------------------------------------------COMMENT
MEDIUM…/infrastructure/offensive-windows-mitigations/SKILL.md1458# -------------------------------------------------------------------COMMENT
MEDIUM…/infrastructure/offensive-windows-mitigations/SKILL.md2493 # ================================================COMMENT
MEDIUM…/infrastructure/offensive-windows-mitigations/SKILL.md6357# =========================================================================COMMENT
MEDIUM…/infrastructure/offensive-windows-mitigations/SKILL.md6361# =========================================================================COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md8673// ── Registry-based CI status query ──────────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md8734// ── Active CI policy file enumeration ───────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md8783// ── Verify Authenticode signature of a binary ───────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md8883// ── Scan for LOLBAS bypass binaries ─────────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md8926// ── Check ASR rule enforcement ──────────────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md8993// ── Test binary execution against WDAC ──────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md10460// ── Enumerate ALL active ETW tracing sessions ───────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md10523// ── Enumerate registered ETW providers via TDH ──────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md10583// ── Check if EtwEventWrite is already patched ───────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md12492// ── IOCTL code decoder ──────────────────────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md12523// ── Enumerate loaded kernel drivers ─────────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md12625// ── Probe known BYOVD driver device paths ───────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md12695// ── Send test IOCTL to a target driver ──────────────────────COMMENT
MEDIUM…s/infrastructure/offensive-windows-boundaries/SKILL.md12786// ── Enumerate driver service entries from registry ──────────COMMENT
Over-Commented Block133 hits · 77 pts
SeverityFileLineSnippetContext
LOWinstall.sh1#!/usr/bin/env bashCOMMENT
LOW.github/workflows/codeql.yml1# For most projects, this workflow file will not need changing; you simply needCOMMENT
LOW.github/workflows/codeql.yml61COMMENT
LOWSkills/crypto/offensive-tls-attacks/SKILL.md221Applications that fail to properly validate TLS certificates create interception opportunities. Common flaws include disCOMMENT
LOWSkills/fuzzing/offensive-fuzzing-course/SKILL.md13615. **Overflow**: Writing 512 bytes into 256-byte buffer = 256 bytes overflowCOMMENT
LOWSkills/fuzzing/offensive-fuzzing-course/SKILL.md1521#COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md321// Some programs behave differently:COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1101# IMPORTANT: Full source info requires debug symbols (-g flag at compile time)COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1201COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1221# # Then re-run the crashCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1361```bashCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1381# RDX 0COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1401# ► 0 0x4141414141414141 NoneCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1421# _timer = {COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1441#00:0000│ rsp 0x7ffcc3436d60 ◂— 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1501#rax=00000000000000d7 rbx=000000000052e6b0 rcx=0000000000000000COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1521#READ_ADDRESS: ffffffffffffffffCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1581# Look for: heap_overflow or HeapFree in the stackCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1941COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md1981# Note: p- steps back to previous "step boundary" (breakpoints, calls),COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md20210:000> dx @$cursession.TTD.Memory(0x14fed8, 0x14fee0, "w")COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2041COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2141```bashCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2161# Call stack shows:COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2181# Step 6: Get details on the free and navigate to itCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2201COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2261# Executable: C:\CrashAnalysisLab\vuln_win_nosym.exeCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md23010:000> kCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2341# Look for function prologueCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2361COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2401COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md26010:000> .scriptrun C:\CrashAnalysisLab\crash_classify.jsCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2621# Rsp: <error reading>COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md26410:000> .exr -1COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md2961# Now set breakpoint on strcpy and continue - next hit is the vulnerable oneCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md3361COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md3781COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5021**Using checksec (pwntools)**:COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5041# Debuginfo: YesCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5101pwndbg> run 1 $(python3 -c "print('A'*200)")COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5121# RIP 0x401225 (stack_overflow+79) ◂— retCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5201# NX: NX unknown - GNU_STACK missingCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5221pwndbg> x/i $ripCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5661# Example output:COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md5801COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md7021# File → Load file → drcov.target.12345.0000.proc.logCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md7081# Example output:COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md7241# [+] Hooked libc free at 0x7a0dddeadd30COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md7501# [+] Hooked strcpy at 0x70b804b8b530COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md7521# [!] TAINTED DATA REACHING SINK!COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md7721# Go back to find the exact UAF accessCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md8161# Shows uninitialized (overflow hasn't happened yet)COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md8781# Number of clusters: 8COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md8921[*] First free doneCOMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md9401# [+] New variant (1): test=1, #0 in strcpy (/home/dev/crash_analysis_lab/vuln_as...COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md9661# Create crash input (150 A's triggers stack overflow)COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10521# [+] Analyzing pocs/stack_crash_min.txt with test case 1...COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10721# Run PoC (starts server automatically)COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10961COMMENT
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md11101COMMENT
73 more matches not shown…
Hallucination Indicators3 hits · 30 pts
SeverityFileLineSnippetContext
CRITICALSkills/web/offensive-ssti/SKILL.md135{{config.__class__.from_envvar.__globals__.__builtins__.__import__('os').popen('id').read()}}CODE
CRITICALSkills/web/offensive-ssti/SKILL.md138{{self._TemplateReference__context.cycler.__init__.__globals__.os.popen('id').read()}}CODE
CRITICALSkills/web/offensive-ssti/SKILL.md278GET /page?name=%24%7Bself.module.cache.util.os.popen('id').read()%7D HTTP/1.1CODE
Excessive Try-Catch Wrapping34 hits · 21 pts
SeverityFileLineSnippetContext
LOWconvert_skills.py161 except Exception as e:CODE
MEDIUMtools/build_manifest.py51 print(f"Error: {SKILLS_DIR} not found", file=sys.stderr)CODE
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md9213 except Exception:CODE
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md9547 except Exception:CODE
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10098 except Exception as e:CODE
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10383 except Exception:CODE
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10617 except Exception as e:STRING
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10771 except Exception as e:STRING
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md10882 except Exception as e:STRING
LOWSkills/exploit-dev/offensive-crash-analysis/SKILL.md11974 except Exception as e:STRING
LOW…ills/exploit-dev/offensive-basic-exploitation/SKILL.md6877except Exception as e:STRING
LOW…ills/exploit-dev/offensive-basic-exploitation/SKILL.md7180except Exception as e:STRING
LOW…ills/exploit-dev/offensive-basic-exploitation/SKILL.md9334 except Exception as e:STRING
LOW…ills/exploit-dev/offensive-basic-exploitation/SKILL.md9352 except Exception as e:STRING
LOWSkills/web/offensive-open-redirect/SKILL.md347 except Exception as e:CODE
MEDIUMSkills/web/offensive-open-redirect/SKILL.md348 print(f"Error testing {test_url}: {e}")CODE
LOW…post-exploitation/offensive-data-exfiltration/SKILL.md76 except Exception: pass # data is in the query itselfCODE
LOW…post-exploitation/offensive-data-exfiltration/SKILL.md89 except Exception: passCODE
LOW…post-exploitation/offensive-data-exfiltration/SKILL.md407 except Exception: passCODE
LOW…s/supply-chain/offensive-dependency-confusion/SKILL.md306 except Exception: passCODE
LOW⚡…/infrastructure/offensive-windows-mitigations/SKILL.md13108 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md8456 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md9790 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md10091 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md10250 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md10559 except Exception:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md10683 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md10763 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md10835 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md12469 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md12508 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md12549 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md13086 except Exception as e:CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md13145 except Exception as e:CODE
Modern AI Meta-Vocabulary5 hits · 14 pts
SeverityFileLineSnippetContext
MEDIUMREADME.md96| [AI Security](#ai-security) | 1 | Prompt injection, jailbreaking, RAG poisoning |CODE
MEDIUMSkills/ai/offensive-ai-security/SKILL.md365### RAG/Vector SystemsCOMMENT
MEDIUMSkills/ai/offensive-ai-security/SKILL.md496### Egress & Provenance for Agents/RAGCOMMENT
MEDIUMSkills/infrastructure/offensive-initial-access/SKILL.md878#### RAG (Retrieval Augmented Generation) Database PoisoningCOMMENT
MEDIUMSkills/infrastructure/offensive-initial-access/SKILL.md1114##### Long-Term RAG Database PoisoningCOMMENT
Fake / Example Data5 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡Skills/fuzzing/offensive-fuzzing-course/SKILL.md1604 uint8_t fake_data[1024];CODE
LOW⚡Skills/fuzzing/offensive-fuzzing-course/SKILL.md1605 memset(fake_data, 'A', sizeof(fake_data));CODE
LOW⚡Skills/fuzzing/offensive-fuzzing-course/SKILL.md1607 process_image(width, height, fake_data);CODE
LOWSkills/fuzzing/offensive-fuzzing-course/SKILL.md16863. **Overwrite**: The loop writes attacker data (`fake_data`) into the adjacent sensitive object.CODE
LOW…s/infrastructure/offensive-windows-boundaries/SKILL.md10121 xmlns:user="placeholder" version="1.0">CODE
Synthetic Comment Markers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHSkills/recon/offensive-osint/SKILL.md348- [Reality Defender](https://realitydefender.com/) — AI-generated content detectionCODE
Slop Phrases1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/codeql.yml56 # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize howCOMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOWconvert_skills.py15CODE
LOWconvert_skills.py167CODE
Unused Imports2 hits · 2 pts
SeverityFileLineSnippetContext
LOWconvert_skills.py217CODE
LOWtools/build_manifest.py8CODE
Hyper-Verbose Identifiers4 hits · 2 pts
SeverityFileLineSnippetContext
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md2478def exploit_with_known_offset():CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md9947def check_speculation_mitigations():CODE
LOW…/infrastructure/offensive-windows-mitigations/SKILL.md9983def exploitation_decision_tree(vbs_data):CODE
LOW…s/infrastructure/offensive-windows-boundaries/SKILL.md8379def enumerate_system_processes():CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWinstall.sh5# Usage:COMMENT