Back to skill

Security audit

test

Security checks for vulnerabilities and agentic risk

Overview

This is a small Git workflow guidance skill with no install steps, executables, hidden persistence, or unrelated data access.

This skill is reasonable to install if you want Git workflow guidance. Review Git commands before running them, especially rebases, branch deletion, and force-with-lease pushes, because those can affect repository history even when used appropriately.

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
  • 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
Findings (2)

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 · AGENTS.md (reported line 47)May include surrounding context.

bash
git fetch origin
git rebase -i origin/main    # squash fixups, reword messages
git push --force-with-lease   # safe force push to your branch

Finishing a Branch

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The instruction 'Reference this agent by name or specialty when you need its expertise' does not define specific trigger phrases or boundaries for when the skill should activate. Because 'specialty' and 'need its expertise' are open-ended, ordinary discussion about Git workflows could match unintentionally.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.