Mechanic

• Outcome: Pass
• Latest audit: May 27, 2026 at 9:13 PM UTC
• Version:
  1.1.0

Overview

This vehicle-maintenance skill is purpose-aligned and transparent, but users should understand it stores sensitive vehicle details and can run scheduled recall checks.

Install only if you are comfortable keeping vehicle records in the workspace and having VIN or vehicle details sent to NHTSA for decoding and recall checks. Keep the mechanic data folder private, avoid storing insurance or policy details unless you need them, and review the weekly cron reminder if you do not want scheduled background checks.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• 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 (5)

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The README states that sensitive vehicle-related data such as VIN, insurance details, service history, location-derived environmental context, and warranty information are stored under the workspace, but it does not warn users about privacy implications or recommend access controls. In a maintenance-tracking skill, this data can enable profiling, location inference, or disclosure of identifying vehicle information if the workspace is shared, synced, or backed up insecurely.

Missing User Warnings

Medium

• Confidence: 79% confidence
• Finding: The README says first use will 'set up a recurring cron job to check in' but does not present this as a security- or privacy-relevant behavior, nor explain scope, frequency, how to disable it, or what commands are scheduled. Persistent scheduled execution increases risk because it creates ongoing autonomous behavior that could continue accessing or processing user data after initial setup, especially in environments where users do not expect background tasks.

Missing User Warnings

High

• Confidence: 95% confidence
• Finding: The skill persistently stores sensitive personal and vehicle data, including VINs, insurance provider, policy number, roadside assistance contact, location history proxies via mileage/service logs, and provider information, but does not present an explicit privacy notice or consent flow. This increases the risk of unintended retention and exposure of sensitive data within the workspace, especially if other tools, users, or future skill operations can access those files.

Missing User Warnings

High

• Confidence: 98% confidence
• Finding: The VIN decode workflow sends the user's VIN to an external NHTSA service without a clear, prior warning or consent step. A VIN is a persistent vehicle identifier that can reveal detailed vehicle attributes and may be linkable to an individual, so transmitting it externally without explicit notice creates a meaningful privacy risk.

Missing User Warnings

High

• Confidence: 97% confidence
• Finding: The recall-monitoring feature transmits VINs or make/model/year data to NHTSA, including potentially during scheduled automated checks, without an explicit warning or opt-in. Automatic recurring external transmission of persistent identifiers is more dangerous because it can happen without a fresh user action and may surprise users who only intended local maintenance tracking.

VirusTotal

64/64 vendors flagged this skill as clean.