# Game Hacking Techniques

> Classify game-cheat implementation surfaces and their defensive implications. Use for authorized threat modeling of memory access, injection, overlays, input, or engine attack surfaces.

- Skill: `neversight/game-hacking-techniques` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add neversight/game-hacking-techniques`
- Raw SKILL.md: https://api.skillmd.com/api/skills/neversight/game-hacking-techniques/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: neversight (https://skillmd.com/u/neversight)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/neversight/game-hacking-techniques

---


# Game-hacking techniques

Use this skill to understand offensive techniques as inputs to defensive research, detection design, or authorized lab analysis. Do not treat the catalog as permission to target third-party systems.

## Topic routing

Read only the reference that matches the task:

- [Taxonomy and core techniques](references/taxonomy-and-core-techniques.md) for privilege levels, manipulation, injection, and cheat categories.
- [Rendering, memory, and input](references/rendering-memory-and-input.md) for overlays, access paths, driver communication, world-to-screen, and input simulation.
- [Platform and evasion](references/platform-and-evasion.md) for EFI, HWID, stack behavior, and anti-detection concepts.
- [Engines and workflow](references/engines-and-workflow.md) for Unity, Unreal, Source, and representative research workflows.
- [Resource map](references/resources.md) for learning material and source attribution.

Use `anti-cheat-systems` for defender architecture, `graphics-api-hooking` for render-pipeline details, and `game-engine-resources` for engine internals. Distinguish observed techniques from hypothetical capability and keep recommendations defensive.