Git Blame

Security checks across malware telemetry and agentic risk

Overview

This is an instruction-only git history audit skill that reads local repository metadata to produce risk reports, with no install-time code or hidden execution.

Install this only for repositories where you are comfortable with the agent reading git history and author metadata. Prefer invoking it explicitly with /git-blame-audit, and treat its risk score as triage guidance rather than proof of malicious code or author intent.

SkillSpector

By NVIDIA
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 (1)

Vague Triggers

Medium
Confidence
92% confidence
Finding
The trigger phrases include broad natural-language requests such as 'is this code risky' and 'who last touched this and is it safe', which can match ordinary developer conversation and cause the skill to activate outside explicit user intent. In an auditing skill, unintended activation can lead to over-collection of repository metadata or execution of local git commands in contexts where the user did not mean to invoke the tool.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal