Back to skill

Security audit

product-video

Security checks for vulnerabilities and agentic risk

Overview

This skill guides paid product-video creation with user approval, price limits, and safeguards against duplicate charges.

Use public product images you are comfortable sharing with Makernice, and approve spending across all clips. Generated results blocked by safety review may still be charged. The sole artifact was fully inspected and scanner coverage was complete; server-side billing caps, retry deduplication, and data handling were not independently verified.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 61)May include surrounding context.

md
## 5. Generate after the user agrees

Only call `generate` after the user has seen the price and said yes. If the user already set a budget and told you to go ahead, you may start without asking again as long as `amount_usd` is within that budget; still use `amount_usd`, not the budget, as `max_cost_usd`.

- `max_cost_usd`: required. Use the approved `amount_usd` from `estimate_cost`, exactly as returned. The job is refused if the price is higher.
- `request_id`: required and unique for every new job, printable ASCII with no spaces, at most 64 characters, for example `mug-orbit-720p-1`. A used id can never be reused for a different job.