ClawHub
Back to skill

Security audit

CLV Tracker — Closing Line Value

Security checks for vulnerabilities and agentic risk

Overview

The skill has a coherent betting-tracker purpose, but its documented command pattern can turn supplied bet fields into executable Python or SQL.

Review this carefully before installing. Only use it with trusted, simple numeric and text inputs, and prefer a revised version that validates odds, uses SQLite parameter binding, documents how stored betting history can be deleted, and removes unused credential/tool requirements until implemented.

A.I.G

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (1)

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:37
Finding

Command and SQL Injection Through Unsafely Interpolated Bet Data

Content
View full analysis
Remediation
View remediation

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

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill explicitly instructs the agent to persist betting data into a local SQLite database under the user's home directory without any warning, consent flow, retention notice, or explanation of what data will remain on disk. Persistent storage of betting history can expose sensitive behavioral, financial, or regulatory information to other local users, backups, or later agent actions, especially because the path is predictable and long-lived.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.