Back to skill

Security audit

Gitignore

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to be a harmless static documentation script, but it is labeled as a Gitignore reference while mostly returning generic devtools boilerplate instead of real .gitignore guidance.

Install only if you are comfortable with a low-impact documentation skill whose content appears generic and unreliable for Gitignore tasks. It does not show credential theft, network access, persistence, or destructive behavior, but users expecting authoritative .gitignore guidance should treat its output skeptically or wait for the publisher to align the script with the advertised purpose.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (5)

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

The code does not perform harmful or hidden actions; it is a simple documentation CLI with no external access. However, its actual content does not accurately match the declared purpose of a Gitignore reference tool. The output text is generic boilerplate about an unspecified 'gitignore' tool/concept, rather than meaningful reference information about .gitignore files, ignore patterns, syntax, matching rules, exceptions, best practices, or implementation patterns. While some command names overlap with the description (intro, quickstart, patterns), the material is materially different in substance, making this a description-behavior mismatch.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/script.sh (reported line 64)May include surrounding context.

sh
## Prerequisites
- Basic understanding of devtools concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

This markdown file defines trigger-like commands such as "intro", "security", "migration", and "performance" without any context, activation constraints, or negative examples. These single common words are overly broad and could cause unintended invocation because the file does not specify when they apply versus ordinary conversation.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The header and help text claim this is a Gitignore reference tool, but the body content describes a generic platform/service workflow. In an agent skill ecosystem, this kind of deceptive labeling increases the risk of misuse, incorrect automation decisions, and trust abuse because callers may invoke the skill expecting authoritative gitignore guidance.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The script is presented as a Gitignore-specific reference tool, but most command output is generic devtools guidance unrelated to .gitignore syntax or usage. This mismatch can mislead downstream agents or users into trusting the tool for a narrowly scoped task when it actually provides inaccurate or irrelevant content, creating a prompt/skill integrity issue rather than direct code execution risk.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.