Back to skill

Security audit

Metadata Naming

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation-only naming guide with no executable behavior, data access, persistence, or hidden authority.

Installers should understand that the skill may steer automation-oriented filenames toward ASCII slugs and no spaces. Use its relaxed mode when preserving localized, human-readable, or mixed-language filenames matters more than strict script portability.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The markdown states "Use by default" for strict mode and then requires "ASCII only," which excludes non-ASCII languages and scripts by default. This is a language/locale policy concern because it imposes an English/ASCII-centric constraint without opt-in or a clearly documented regional or technical limitation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The document states 'ASCII only' as a strict-mode requirement, which is a natural-language locale/language constraint. Because the file does not present this as an optional user choice or justify it as a region-specific/compliance requirement, it can conflict with policy against forcing a specific language/locale without opt-in.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.