Back to skill

Security audit

subclip-project-log

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill benign with high confidence: it found one anti-refusal pattern, but judged it unlikely and not purpose-related, while the other verdict dimensions are OK.

The verdict is benign, not a guarantee of zero risk. Scanners inspected the single Markdown component with complete reported coverage; consider the anti-refusal flag in context before installing.

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
  • 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)

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
85% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

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

md
## When you start

1. To choose a project, call `list_projects`. Each project comes with its brief, the latest summary, duration, canvas, layer counts and a small thumbnail image. Use `query` to search names, briefs and summaries; use `limit` and `cursor` to page.
2. A thumbnail with state `black` is an old or failed capture: do not judge the project by it. Read the brief, or look at a real frame.
3. Before you change a project someone else touched, call `get_project_director_brief` (the brief plus the latest trail entries) and, if you need more history, `get_project_log`.
4. On your first call of the session pass `userRequest` with what the user asked for, in their words.