Back to skill

Security audit

Git Cli 1.0.0

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Git CLI helper that discloses normal Git operations and explicitly warns against destructive commands.

Installers should still treat Git mutation commands with care: this skill may help stage, commit, pull, push, stash, or switch branches when asked, so review commands before running them, especially anything that discards local work or rewrites remote history.

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
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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 (3)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
65% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · SKILL.md (reported line 39)May include surrounding context.

md
- Prefer **read-only commands** first (`git status`, `git diff`, `git log`) before suggesting changing commands.
- Avoid destructive suggestions such as:
  - `git reset --hard`
  - `git clean -fdx`
  - `git push --force`
- Only mention or recommend such commands if the user explicitly asks and understands the risk.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · SKILL.md (reported line 40)May include surrounding context.

md
- Prefer **read-only commands** first (`git status`, `git diff`, `git log`) before suggesting changing commands.
- Avoid destructive suggestions such as:
  - `git reset --hard`
  - `git clean -fdx`
  - `git push --force`
- Only mention or recommend such commands if the user explicitly asks and understands the risk.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
70% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · SKILL.md (reported line 41)May include surrounding context.

md
- Avoid destructive suggestions such as:
  - `git reset --hard`
  - `git clean -fdx`
  - `git push --force`
- Only mention or recommend such commands if the user explicitly asks and understands the risk.

## Common Workflows

Static analysis

No suspicious patterns detected.