ClawHub
Back to skill

Security audit

frontend-design

Security checks for vulnerabilities and agentic risk

Overview

This is a frontend design guidance skill with no code execution, network behavior, or hidden install mechanism; the only notable caution is that it suggests using remembered design context for personalization.

Install this if you want stronger visual-design guidance for frontend work. Be aware that it may encourage the agent to use remembered preferences or prior design context as inspiration, so avoid enabling or applying such memory when the current project is sensitive or unrelated.

A.I.G

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

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

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
55% 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 53)May include surrounding context.

md
Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.

Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.

Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly instructs the agent to use information from memory about the user's preferences, context, or prior designs when generating output. That creates a real risk of cross-turn or cross-task disclosure of sensitive or unnecessary user data in the response, especially if memory contains details unrelated to the current request.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The suggestion to jot down notes for future passes encourages retaining user- or task-specific information beyond the immediate interaction. Even though phrased as productivity advice, it can normalize persistent storage of contextual details that may later be surfaced improperly or retained longer than necessary.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.