Individual skill
pojia-game-security
Defensive game security and cheat research covering external and internal cheat architecture, trainers, memory tampering, ESP/overlay, aim automation, injection and hooks, packet manipulation, asset/config modification, anti-cheat telemetry, integrity, server authority, Unity IL2CPP, Unreal, incident analysis, and detection validation. Use when Codex receives a game binary, cheat sample, anti-cheat design, suspicious telemetry, memory offsets, hooks, overlays, player reports, or needs to understand how game abuse works in order to detect, reproduce in a lab, harden, or investigate it.
skills/pojia-game-security/SKILL.md
Source commit b6785d53ca5133974b6d9c987f13f606df28cc38
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 128
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- integrity-protection Repository topic
- macos Repository topic
- persona Repository topic
- prompt-injection Repository topic
- workbuddy Repository topic
- automation Repository topic
- codex Repository topic
- codex-cli Repository topic
- no-dependencies Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,421 bytesagents/openai.yamlasset · 257 bytesreferences/anti-cheat-design.mddoc · 927 bytesreferences/cheat-architecture.mddoc · 1,653 bytesreferences/engine-security.mddoc · 890 bytesreferences/incident-analysis.mddoc · 729 bytesscripts/integrity_manifest.pyruns · 2,067 bytesscripts/telemetry_analyze.pyruns · 3,014 bytes
Read excerpt
# Pojia Game Security
Analyze the abuse path from trust boundary to observable behavior, then implement detection and hardening.
## Start
1. Identify engine, platform, architecture, network model, authoritative state, anti-cheat components, and available artifacts.
2. Classify the technique: external memory, injected/internal, input automation, overlay/ESP, runtime patch, packet/protocol, asset/config, kernel/driver, DMA/hardware, or account/economy abuse.
3. Map required access, modified state, data sources, persistence/lifecycle, and observable artifacts.
4. Reproduce only the minimum behavior needed to validate detection or a defensive hypothesis.
## Select references
- Cheat categories, data flows, and observables: read `references/cheat-architecture.md`.