Security audit

RoughCut

Security checks for vulnerabilities and agentic risk

Overview

The skill has a coherent video-editing purpose, but it runs an unpinned external local repository script and may ask for a raw Gemini API key without enough handling guidance.

Install only if you trust and control the referenced RoughCut checkout. Before running, verify the repository origin and commit yourself, avoid running from an arbitrary modified `repo_root`, and provide `GEMINI_API_KEY` through a local environment variable only when fluff removal is explicitly enabled. Treat direct download URLs and generated debug bundles as potentially sensitive because they may contain or derive from your video content.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
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)

T08 · Insecure Dependencies

Error

Location: SKILL.md:35
Finding: Execution of Unpinned Code from an External Repository
Content: View full analysis
Remediation: View remediation

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
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

Medium

Category: Not specified by scanner
Confidence: 88% confidence
Finding: The skill explicitly instructs the agent to ask the user for a GEMINI_API_KEY and use it for fluff removal, but it does not provide clear guidance on secure handling, storage, scope limitation, or warnings about sharing secrets with the agent runtime. In an agent setting, requesting credentials can expose users to unnecessary secret disclosure, accidental logging, reuse in unintended contexts, or persistence in transcripts and environment configuration.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.