security-audit

Audit game codebases for security vulnerabilities and generate prioritized remediation reports.

14|1|Updated Apr 12, 2026

Search Tags:#security #vulnerability #audit #compliance #review #game #cheat

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill security-audit-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/security-audit
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill security-audit-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies and prioritises security weaknesses in game code—such as save‑file tampering, network exploits, input validation gaps, data exposure, cheat vectors, and vulnerable dependencies—so teams can remediate them before public release or multiplayer launch.

Core Features & Use Cases

Parses arguments to select audit scope (full, network, save, input, quick).
Spawns a dedicated security‑engineer subagent that inspects source files, assets, and configuration across six audit categories.
Classifies findings by severity, generates a structured markdown report, and integrates the report as a required artefact for the Polish → Release gate.
Ideal for studios needing a repeatable, automated security check before shipping a game or adding online features.

Quick Start

Run security-audit in the repository root to start a full security audit of the game.

Frequently Asked Questions about security-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit my game codebase for security vulnerabilities before release?▼

To audit game codebase security vulnerabilities, a dedicated subagent inspects source files, assets, and configuration across six categories—save, network, input, data exposure, cheat, and dependencies—to classify findings by severity and produce a prioritized remediation report.

What security risks should I check before launching multiplayer game features?▼

Before launching multiplayer game features, you should check for network exploits, save-file tampering, input validation gaps, data exposure, cheat vectors, and vulnerable dependencies, classifying findings by severity to prioritize remediation before public release.

Can I run a security audit focused only on network or save file scopes?▼

Yes, you can run a security audit focused on network or save file scopes by parsing arguments to select full, network, save, input, or quick scopes, allowing targeted evaluation of specific security categories during pre-release or multiplayer feature development.

Does the security audit require specific engine or language detection to run?▼

The security audit requires engine and language detection from technical preferences to evaluate save, network, input, data exposure, cheat, and dependency categories using a dedicated security-engineer subagent within the repository root.

What is the best way to block cheat vectors and input validation gaps in games?▼

The best way to block cheat vectors and input validation gaps is to spawn a dedicated security-engineer subagent that inspects source files across six audit categories, classifies findings by severity, and generates a structured markdown report for prioritized remediation.

How do I integrate a security remediation report into a release gate?▼

To integrate a security remediation report into a release gate, generate a structured markdown report classifying findings by severity, which becomes a required artefact for the Polish to Release gate before public release or multiplayer launch.