Back to skill

Security audit

AI Commit Message Generator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Git commit helper; it can create or amend commits, which is expected for its purpose but should be used only after reviewing staged changes.

Before installing, understand that /commit may create a real Git commit and /commit --amend may alter the latest commit. Review staged files with git diff --staged and use /commit --dry-run when you only want a proposed message.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The manifest says the skill analyzes staged changes and generates commit messages, but the documented commands also perform state-changing actions like git commit and --amend. This scope expansion is dangerous because a user or calling agent may treat the skill as read-only analysis when it can actually persist changes or rewrite recent history.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The command list exposes /commit -m and /commit --amend, both of which modify repository state, but the skill does not clearly warn that these actions create commits or rewrite the previous one. In an agent setting, missing warnings can cause unintended persistence of sensitive code or accidental history alteration.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The workflow proceeds from analysis directly to executing git commit, but it lacks an explicit safety boundary that this step will permanently record all staged changes in version control. That creates a real risk of unintended commits, including secrets, incomplete work, or policy-violating code, especially if an autonomous agent follows the workflow literally.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The initial-commit edge case suggests automatically creating a commit when HEAD does not exist, without a warning that this changes repository state. Automatic first commits are especially risky because users may not realize all staged content, including accidental files, will become part of project history.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

The manifest centers on analyzing already staged changes via git diff --staged. But the edge-case guidance says to run git status and prompt the user about staging all changes, expanding the skill's role from staged-diff analysis into helping decide what to stage.

Content

No source excerpt is available for this finding.