glm-plan-usage

• Outcome: Pass
• Latest audit: May 28, 2026, 1:01 PM
• Version:
  1.0.1

Overview

This skill is a disclosed GLM usage checker, but users should handle the API key and cleanup commands carefully.

Install only from a source you trust, review scripts/query-usage.sh before running it, protect ~/.openclaw/openclaw.json, avoid commands that print full API keys, verify rm -rf paths before cleanup, and add the cron job only if you want scheduled local usage checks.

SkillSpector

By NVIDIA

Vulnerability Patterns

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

Findings (5)

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The troubleshooting command explicitly prints the raw API key to the terminal, which can leak credentials through shell history, terminal scrollback, screen sharing, logging, or copied diagnostics. Even though this is in documentation rather than code, it instructs users to expose a secret in plaintext and can directly lead to credential compromise.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The uninstallation instructions include a recursive force-delete command without any warning about irreversibility or guidance to verify the target path first. In an installation guide, this creates a real safety issue because users may run destructive commands verbatim and permanently remove files if the path is wrong or unexpectedly expanded.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The upgrade flow creates a backup and then instructs users to delete it without warning that local modifications or rollback data will be lost. This is a genuine unsafe practice in documentation because users may assume the backup remains available when troubleshooting or reverting.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The Chinese uninstallation section repeats the same force-delete command without a clear warning about permanent deletion. This is a true documentation safety issue for the same reason as the English section: users may execute it directly and lose data irreversibly.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The Chinese upgrade instructions advise deleting the backup copy after reinstalling, but do not warn that rollback data and local changes will be permanently lost. This is a real unsafe omission in lifecycle documentation, especially for users relying on the backup for recovery.

VirusTotal

66/66 vendors flagged this skill as clean.