Back to skill

Security audit

Game Dev First Steps

Security checks for vulnerabilities and agentic risk

Overview

This is a text-only game planning helper with no code execution, credential use, persistence, or hidden data access.

Safe to install if you want lightweight advice on scoping and sequencing an early game project. Treat it as planning guidance, not engine-specific or legal/business advice, and avoid sharing confidential project details unless you are comfortable doing so.

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Confidence
95% confidence
Finding
The manifest description says to use the skill when someone asks 'how to start making a game,' 'what to build first,' or 'how to approach development order,' which are broad phrasings likely to match many general conversations. It does not provide exclusion conditions or negative examples to clarify when this skill should not activate versus other planning, production, or game-design skills.

Static analysis

No suspicious patterns detected.