Back to skill

Security audit

git-conventions

Security checks for vulnerabilities and agentic risk

Overview

This is a small git workflow convention skill that gives disclosed commit and push guidance without hidden code, persistence, or data access.

Install this only if you want your agent to follow these git conventions, including English commit messages, signed-off commits, and prompting about pushing after local commits. Review whether those workflow rules match your repository before relying on it.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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
Findings (3)

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 26)May include surrounding context.

md
1. **Language**: Use English only for git commit messages.

2. **Force Push**: Always confirm before `git push --force`.

3. **Sign-off**: Include `--signoff` flag with all commits.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The description says to use the skill when 'making git commits, pushing changes, or performing git operations.' The phrase 'performing git operations' is very broad and overlaps with many ordinary repository actions, making it unclear when the skill should or should not activate.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The instruction 'Use English only for git commit messages' imposes a language policy unconditionally. This is a natural-language policy concern because it forces a specific language without opt-in, alternative support, or a documented regional/compliance reason.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.