security-audit

Audit game codebases and assets for security vulnerabilities across saves, networking, and dependencies.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill security-audit-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/security-audit
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill security-audit-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically discovers and prioritizes security vulnerabilities in a game's codebase and assets, covering save tampering, cheat vectors, network exploits, data exposure, and input validation gaps so teams can fix blocking issues before release.

Core Features & Use Cases

  • Multi-area coverage: Scans save/serialization, network/multiplayer, input validation, data exposure, cheat vectors, and third-party dependencies.
  • Coordinated audit workflow: Spawns a security-engineer task to run targeted grep/glob checks, aggregate findings, classify by severity and status, and produce a formal remediation plan.
  • Gate integration and reporting: Outputs a prioritized markdown report for production and enforces a Polish → Release gate requiring remediation of critical and high findings.
  • Use Case: Run before any public release or enabling multiplayer to ensure no trivially-exploitable cheats or data leaks remain.

Quick Start

Run the security-audit skill in full mode to scan the project and produce a prioritized markdown report saved to production/security/security-audit-[date].md.

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's codebase for security vulnerabilities before release?

To perform a game security audit, run the skill in full mode to search source and asset directories, spawn a security-engineer task for targeted checks, and output a prioritized markdown remediation report.

What security issues should I check before enabling multiplayer in my game?

Before enabling multiplayer, scan for network exploits, cheat vectors, and data exposure by running a coordinated audit that classifies severity and enforces a Polish to Release remediation gate.

Can I scan my game's save and serialization systems for tampering vulnerabilities?

Yes, you can scan save and serialization systems for tampering vulnerabilities using targeted grep and glob checks across source directories, aggregating findings by severity and status.

Does the security audit check third-party dependencies for known exploits?

Yes, the security audit checks third-party dependencies for known exploits alongside save files, networking, input validation, data exposure, and cheat vectors across the codebase.

What is the best way to prioritize game security findings for production release?

The best way to prioritize game security findings is to classify them by severity and status, producing a formal markdown remediation plan that blocks release until critical and high findings are fixed.

When should I run a game security audit during development?

Run a game security audit during pre-release checks, multiplayer launches, save and serialization changes, and after implementing systems that read from disk or network to catch blocking issues.