TOSR Publish Then Update Test

• Outcome: Review
• Latest audit: May 29, 2026, 9:27 PM
• Version:
  0.1.1

Overview

This Git workflow helper mostly matches its purpose, but it contains an unsafe instruction to automatically stage and commit all current changes before user approval.

Install only if you are prepared to override the unsafe auto-commit behavior. Before using it, require explicit approval for every `git add`, `git commit`, `git pull`, and `git push`; review `git status` and the staged diff; scan for secrets; and confirm the remote, branch, and account before any push.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Intent-Code Divergence

High

• Confidence: 97% confidence
• Finding: This is a real safety issue because the skill states that Git operations require explicit user confirmation, yet later instructs an automatic commit of existing changes before asking. That contradiction can cause unauthorized repository mutations, accidental inclusion of sensitive or incomplete work, and loss of user control over version history.

Missing User Warnings

High

• Confidence: 98% confidence
• Finding: Automatically running git add . and git commit without a warning or confirmation is dangerous because it can capture unintended files, secrets, large artifacts, or unrelated work. In a skill specifically designed for commit/push workflows, this is more dangerous because users may trust it to handle source-control operations safely and may not notice silent staging of all changes.

VirusTotal

60/60 vendors flagged this skill as clean.