ClawHub
Back to skill

Security audit

desgin

Security checks for vulnerabilities and agentic risk

Overview

This is a frontend design guidance skill made of Markdown references, with no hidden execution, persistence, credential use, or unrelated data access found.

Before installing, treat this as a style and process guide for frontend design. Its guidance is opinionated, so adapt copy, typography, and approval workflow to your product, brand, locale, and team conventions.

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

Anti-Refusal Statement

High
Category
Anti-Refusal
Content
## Errors

- Say what happened and what to do next.
- Do not apologize. Do not blame the user.
- Be specific: "Enter a date after 2024-01-01" not "Invalid date."

## Empty States
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.

Natural-Language Policy Violations

Low
Confidence
77% confidence
Finding
Line L42 uses prescriptive natural language that could be interpreted as forcing a single writing convention across all contexts. Because the file does not mention user opt-in or locale-specific exceptions, this may conflict with organizational language or locale flexibility requirements.

Static analysis

No suspicious patterns detected.