Security audit

Phone Charger Stash Map

Security checks for vulnerabilities and agentic risk

Overview

This prompt-only skill is a household charger organization checklist and does not ask for credentials, run code, use the network, or create persistence.

Before installing, users should know this is an English prompt-only helper for organizing physical chargers. Do not enter device passcodes, account details, serial numbers, phone numbers, tracking settings, or monitoring information; the skill itself tells the agent to avoid those details.

A.I.G

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

SkillSpector

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 (3)

Natural-Language Policy Violations

Medium

Confidence: 97% confidence
Finding: The checklist explicitly states "Language is English only," which is a natural-language policy constraint. The file does not indicate user choice, opt-in, or a documented region/compliance justification for restricting the skill to English.

Vague Triggers

Low

Confidence: 82% confidence
Finding: This markdown file includes the example input "I need a charger stash map for my house," which reads like a general everyday request rather than a tightly scoped activation phrase. Because the document does not provide explicit trigger constraints or negative examples here, the invocation boundary may be interpreted too broadly.

Natural-Language Policy Violations

Low

Confidence: 95% confidence
Finding: The manifest sets `language: "en"`, which expresses a fixed language choice. The file does not offer the user a language/locale option or explain why English is required for a region-specific or compliance-related reason.

Static analysis

No suspicious patterns detected.