Back to skill

Security audit

git-commit-helper

Security checks for vulnerabilities and agentic risk

Overview

This skill helps create git commits after confirmation, and its repository-changing behavior is disclosed and aligned with that purpose.

Install this only if you want the agent to help commit repository changes. Review the displayed file scope and commit message carefully before approving, especially because choosing the all-files path stages the whole working tree.

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
95% confidence
Finding

The skill advertises broad activation phrases such as "commit" and common everyday-language equivalents, which can cause the agent to invoke a code-committing workflow from ambiguous user input. In this context, accidental activation is meaningful because the skill can lead to repository-modifying actions after only conversational confirmation, increasing the chance of unintended commits or misuse in the wrong context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The description embeds Chinese trigger instructions alongside English guidance without stating that the user may choose their preferred language. If organizational policy requires language or locale choice rather than implicit enforcement, this can be interpreted as a natural-language policy issue.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.