security-auditor

Audit web-based game engine integrations for security risks and remediations.

1|Updated Feb 6, 2026

Search Tags:#security #dependencies #auditing #csp #wasm #headers #inputs

Ready to run

npx skills add https://github.com/hdkz-dev/multi-game-engines --skill security-auditor-hdkz-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-auditor
Source: https://github.com/hdkz-dev/multi-game-engines/tree/main/.agent/skills/security-auditor
Command: npx skills add https://github.com/hdkz-dev/multi-game-engines --skill security-auditor-hdkz-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps identify and remediate security risks in game-engine projects and web apps, focusing on CSP misconfigurations, dependency vulnerabilities, wasm safety, input validation, and header hygiene.

Core Features & Use Cases

CSP review and hardening: remove unsafe directives and ensure strict policies.
Dependency vulnerability management: run pnpm audit and manage overrides.
Wasm security and isolation: validate wasm sources and isolate untrusted code.
Input sanitization and headers hygiene: validate inputs and ensure security headers.

Quick Start

Perform a security audit of the current repository and report findings.

Frequently Asked Questions about security-auditor

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

FAQPage Schema

How do I audit security vulnerabilities in a web-based game engine project?▼

To audit security vulnerabilities in a web-based game engine, review CSP policies, run dependency checks with pnpm audit, validate wasm isolation, sanitize inputs, and configure security headers. This identifies risks across adapters and external dependencies while providing actionable remediations.

What is the best way to harden Content Security Policy for wasm modules?▼

Hardening Content Security Policy for wasm involves removing unsafe directives and enforcing strict policies. You must validate wasm sources, isolate untrusted code, and apply appropriate header configurations to maintain secure defaults across the repository's wasm modules and adapters.

How does pnpm audit help manage dependency vulnerabilities in game engine integrations?▼

pnpm audit helps manage dependency vulnerabilities by scanning the project for known security flaws and managing overrides. It checks the repository's external dependencies to ensure the web-based game engine integration maintains a strong security posture against package-level threats.

Do I need git-secrets to secure my game engine repository?▼

You need git-secrets to prevent committing sensitive data like API keys into your game engine repository. Using it alongside pnpm audit and strict CSP header configurations ensures comprehensive coverage against both dependency vulnerabilities and accidental secret leakage.

Can I use this approach to secure untrusted wasm code in my game adapters?▼

Yes, you can secure untrusted wasm code in game adapters by validating wasm sources and ensuring strict isolation. The process applies targeted security checks across the repository's wasm modules to mitigate integration risks and enforce secure defaults.

Why does my web game engine fail input validation and header hygiene checks?▼

Your web game engine fails input validation and header hygiene checks due to unsanitized user inputs and missing or misconfigured security headers. Applying strict input sanitization and appropriate header configurations resolves these security posture issues.