ClawHub
Back to skill

Security audit

Conventional Commits

Security checks for vulnerabilities and agentic risk

Overview

This skill is a Markdown-only guide for formatting commit messages and shows no evidence of code execution, data access, persistence, or hidden behavior.

Install this if you want agents to prefer Conventional Commit formatting. Be aware it may nudge commit-message discussions toward that format even when a repository does not require it.

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

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The description says to use the skill when the user "mentions commits, git commits, or commit messages," which is broader than a clear invocation condition for formatting help. This can cause unintended activation during general discussion about commits rather than when the user wants a commit message formatted in Conventional Commits style.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
76% confidence
Finding

The instruction "Format all commit messages according to" the specification imposes a universal formatting policy in natural language. While not a language-locale issue, this is an organizational-style mandate presented without any opt-in or context about whether the repository actually requires Conventional Commits.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.