Back to skill

Security audit

AI Agent Readiness

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill benign because the reported finding appears in an accessibility checklist, while scans reported no other findings; confidence is medium and evidence is incomplete.

The verdict is benign, but benign does not mean risk-free. Skillspector scanned the reported component but marked coverage partial because several local path-like references could not be resolved; treat the assessment as incomplete when deciding whether to install.

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

Anti-Refusal Statement

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

md
ibility tree for browsing agents.** Browser agents work from screenshots, the DOM and the accessibility tree. Use Chrome DevTools' accessibility tree, Lighthouse, or Playwright's `ariaSnapshot()`.
   - Every button and link has an accessible name. Icon-only buttons without `aria-label` show up as "button" with no name: `Fix next`, or `Fix now` on signup and checkout.
   - Form fields have real `<label>` elements (placeholders don't count), clear error messages in text, and no time-limited steps without warning.
   - Core actions use real `<button>`, `<a href>`, `<select>` and `<input>`; custom widgets have correct ARIA roles and states. A `div` with a click handler is invisible as a control.
   - Pricing is readable as text: plan name, price, currency, billing period, what's included and limits. Monthly/annual toggles keep both prices in the DOM. "Contact us" pricing is a business choice; say so on the page.
   - Nothing essential depends on hover, drag, infinite scroll without paginat