Security audit

Clip

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it says: it downloads a YouTube video, clips the requested range, and saves it locally, with a minor temporary-file safety weakness to be aware of.

Install only if you are comfortable with the skill downloading media from supplied URLs and writing clips to ~/Desktop/Clips. Use unique clip names to avoid overwriting outputs, and avoid running it in a hostile shared-machine environment because its temporary work directory is predictable.

A.I.G

Vulnerability Patterns

Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (1)

T09 · Insecure Skill Coding Practices

Warning

Location: clip.sh:7
Finding: Predictable Shared Temporary Directory Enables File Races and Symlink Attacks
Content: View full analysis
Remediation: View remediation

SkillSpector

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

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 92% confidence
Finding: This markdown file describes file-creating and file-deletion behavior, but presents it as ordinary operation without an explicit caution or warning to the user about modifying local files. Under the markdown-specific warning rule, behaviors affecting user data or system state should be clearly disclosed as warnings, especially the cleanup deletion step.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.