Bypassing Binary Exploitation Mitigations

Bypassing Binary Exploitation Mitigations is a Quality skill for Claude Code, published by xalgord in xalgorix.

852 stars153 forkson xalgord/xalgorixAdded 2026/08/12+1% in starsRepository updated 2026/08/11

ai-agentai-securityautomationautonomous-pentestingbug-bountycybersecurityethical-hackinggolangpenetration-testingpentestpentesting-toolsreconsecuritysecurity-researchsecurity-toolstypescriptvulnerability-detectionvulnerability-scanner

Install in seconds

Install Bypassing Binary Exploitation Mitigations

Copy Bypassing Binary Exploitation Mitigations into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/xalgorix/xalgorix/tree/main/internal/tools/skills/data/binary-exploitation/bypassing-binary-exploitation-mitigations ~/.claude/skills/bypassing-binary-exploitation-mitigations

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/xalgorix/xalgorix.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: internal/tools/skills/data/binary-exploitation/bypassing-binary-exploitation-mitigations/SKILL.md in xalgord/xalgorix
Installs to: ~/.claude/skills/bypassing-binary-exploitation-mitigations
Collection: One of 51 skills cataloged from this repository
Category: Quality — 1354 skills

What Bypassing Binary Exploitation Mitigations does

Bypassing Binary Exploitation Mitigations outlines how to identify and defeat protections like ASLR, PIE, canaries, NX, and RELRO during authorized exploitation. Use it when a memory-corruption bug is blocked by common binary hardening measures.

Bypassing Binary Exploitation Mitigations is cataloged under Quality on DirSkills. Bypassing Binary Exploitation Mitigations comes from a repository tagged ai-agent, ai-security, automation, autonomous-pentesting and bug-bounty.

Documentation

README

Excerpt

Bypassing Binary Exploitation Mitigations

When to Use

At the start of any authorized binary exploitation engagement, to profile which protections (ASLR, PIE, canary, NX/DEP, RELRO) are active and plan the exploit path accordingly.
When a working memory-corruption primitive is blocked by a mitigation: a canary aborts the process, NX prevents shellcode, PIE/ASLR randomizes gadget addresses, or Full RELRO makes the GOT read-only.
When deciding what to leak (libc pointer, PIE base, canary) and how (format string, ret2plt, arbitrary read, brute force in a forked server).

Critical: Concepts/Steps Most Often Missed

This is the opening of the README. Read the full README on GitHub.

Commands Bypassing Binary Exploitation Mitigations provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/atexit
/syscall

Frequently asked about Bypassing Binary Exploitation Mitigations

What else does xalgord publish alongside Bypassing Binary Exploitation Mitigations?
Bypassing Binary Exploitation Mitigations is one of 51 skills that DirSkills catalogs from xalgord/xalgorix, the repository it ships in. Its siblings there include AFL++ Fuzzing, AI Security Guardrails and AI-Assisted Vulnerability Discovery. Each one is a separate skill with its own page in this directory, installs the same way Bypassing Binary Exploitation Mitigations does, and is maintained by xalgord in that same repository. The rest of the collection is listed on the xalgord/xalgorix page.
How does Bypassing Binary Exploitation Mitigations compare to other Quality skills?
Bypassing Binary Exploitation Mitigations ranks #918 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Bypassing Binary Exploitation Mitigations against them. Open each page to compare what they document and how they install.