Back to skill

Security audit

Hook Writer

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only writing skill for creating social-media hooks, with no executable code or hidden high-impact behavior found.

Installers should expect this skill to read brand and voice guidance files when available and to activate on broad hook-writing requests. It appears suitable for low-risk copywriting use; review generated hooks for truthfulness and brand/compliance fit before publishing.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (4)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrases are broad and include common natural-language requests such as "hook for this," "opening line," and "make this scroll-stopping," which could cause the skill to activate unintentionally in ordinary conversation. Misrouting user intent to this skill can lead to incorrect task execution, bypassing more appropriate skills or workflows and degrading reliability.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

This is a JSON manifest/evals file, so vague-trigger checks apply. The example input "Give me a few hook options for this post." is broad everyday phrasing and does not define any activation constraint, which could encourage unintended invocation if used as a trigger pattern.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
79% confidence
Finding

Inputs such as "Write a hook for our launch.", "Write me a scroll-stopping hook.", and similar generic requests are common conversational phrasing rather than narrowly scoped activation language. In a manifest-like test file, the lack of explicit trigger constraints or negative examples makes it unclear when the skill should activate versus when a general writing assistant should respond.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

Lines L04-L05 prescribe a specific writing voice ('blunt indie-founder voice') and require outputs to use the loaded voice.md. This is a natural-language policy concern because it forces a stylistic/locale-related constraint on output without indicating user selection or opt-in.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.