ClawHub
Back to skill

Security audit

Fossil Record

Security checks for vulnerabilities and agentic risk

Overview

This skill is a markdown-only guide for local git-history analysis, with one broad activation phrase users may want to narrow.

Install only if you are comfortable letting the agent inspect local git history for the repository being discussed. Consider narrowing the activation wording so casual questions like "why?" do not trigger history analysis outside explicit code-archaeology requests.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (1)

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger phrase "When someone asks 'why?'" is overly broad and can cause this skill to activate in many unrelated contexts. Broad auto-invocation criteria increase the chance the agent will perform repository-wide history analysis unnecessarily, which can expose internal project context, consume resources, or steer the conversation away from the user's actual intent.

Static analysis

No suspicious patterns detected.