Back to skill

Security audit

qui-conventional-commits

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Conventional Commits formatting guide with no executable behavior or privileged access.

Before installing, understand that the skill may activate for broad discussions about commits, not only explicit requests to draft a commit message. That may be mildly intrusive, but the reviewed artifact does not perform actions, access data, or install anything beyond providing commit-message formatting guidance.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The description says to use the skill when 'the user mentions commits, git commits, or commit messages,' which is an expansive activation condition for a markdown skill. This can trigger on general discussion about commits rather than clear intent to format or generate a commit message, and the file does not provide exclusion conditions or negative examples to narrow scope.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The guidance includes 'When the user asks about commit messages or git commits,' which is broad enough to capture many ordinary help requests unrelated to applying Conventional Commit formatting. Because no constraints distinguish formatting requests from general git discussion, the trigger scope remains underspecified.

Content

No source excerpt is available for this finding.