anti-cheat-systems — Claude Code skill
anti-cheat-systems maps anti-cheat architecture, detection signals, telemetry, and enforcement tradeoffs. Use it for system-level game security questions.
MIT 326 installs ★ 3,784 updated 2026-10-25
npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a claude-codeWhat anti-cheat-systems does
This skill frames an anti-cheat review around the protected asset, attacker capability, observation point, detector, and enforcement authority. It also separates confirmed product behavior from broader defensive patterns, which helps keep system-level claims grounded.
Its topic map points to material on client, kernel, and backend layers, memory, processes, behavior, and input signals. Other sections cover threat research, bypass categories, telemetry, input provenance, detector operations, and network evidence. Questions dominated by DMA, Windows kernel, graphics APIs, mobile protection, or game servers belong with the narrower skills listed in the guide.
What it helps with
- map the layers of an anti-cheat design
- link detection signals to observation points
- weigh evidence for a suspected cheat
- plan telemetry for defensive analysis
- compare enforcement tradeoffs
Example prompts for the agent
- Map this anti-cheat design by protected asset, attacker capability, observation point, detector, and enforcement authority.
- Review the client, kernel, and backend signals for cheat detection, separating confirmed product behavior from general defensive patterns.
- Assess the telemetry and enforcement tradeoffs here; route a DMA-specific question to
dma-attack-techniques.
How to install anti-cheat-systems
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a claude-code2Manually: put the files in place
~/.claude/skills/anti-cheat/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/anti-cheat/
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a codex2Manually: put the files in place
.agents/skills/anti-cheat/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a cursor2Manually: put the files in place
.cursor/skills/anti-cheat/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gmh5225/awesome-game-security .claude/skills/anti-cheat2Manually: put the files in place
.github/skills/anti-cheat/SKILL.md1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a gemini-cli2Platform CLI
gemini skills install https://github.com/gmh5225/awesome-game-security --path .claude/skills/anti-cheatManually: put the files in place
.devin/skills/anti-cheat/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about anti-cheat-systems
How do I install anti-cheat-systems in Claude Code?
Run npx skills add gmh5225/awesome-game-security --skill anti-cheat-systems -a claude-code, then run npx skills add gmh5225/awesome-game-security --skill anti-cheat -a claude-code. The skill file is placed at ~/.claude/skills/anti-cheat/SKILL.md.
What does anti-cheat-systems do?
It analyzes layered anti-cheat architecture, detection evidence, telemetry, and the tradeoffs behind enforcement decisions.
Which anti-cheat topics does it cover?
It routes questions about products, client, kernel, and backend layers, memory, processes, behavior, input, and network evidence. DMA, Windows kernel, graphics, mobile, and game-server details use narrower skills.
Source text
SKILL.md · MIT
--- name: anti-cheat-systems description: Analyze layered anti-cheat architecture, detection evidence, telemetry, and enforcement tradeoffs. Use for system-level defense questions; use narrower skills for DMA, kernel, graphics, mobile, or server details. --- # Anti-cheat systems Map the protected asset, attacker capability, observation point, detector, and enforcement authority. Separate confirmed product behavior from general defensive patterns. ## Topic routing - [Architecture and detection](references/architecture-and-detection.md) for products, client/kernel/backend layers, memory, process, behavior, and input signals. - [Research and threats](references/research-and-threats.md) for analysis methods, bypass categories, platform interactions, protection, telemetry, and ethics. - [Repository map](references/repository-map.md) and [repository resources](references/repository-resources.md) for collection-backed source selection. - [Input provenance](references/input-provenance-and-measurement.md), [detector operations](references/detector-operations.md), or [network evidence](references/network-environment-evidence.md) for those specific evidence questions. Use `dma-attack-techniques`, `windows-kernel-security`, `graphics-api-hooking`, `mobile-security`, or `game-server-security` when that boundary dominates. Apply `game-security-research-rigor` to consequential or disputed claims.
© gmh5225 · MIT · gmh5225/awesome-game-security