memo-collect

Security checks across malware telemetry and agentic risk

Overview

This is a simple local memo skill; its main risk is accidental note deletion because deletes happen immediately by number.

Install only if you are comfortable with a local memo file being created and updated on disk. Avoid storing secrets or hard-to-recreate information in it, and be careful when asking the agent to mark numbered memos complete because deletion has no documented recovery step.

SkillSpector

By NVIDIA

Vulnerability Patterns

Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
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

Findings (2)

Vague Triggers

Medium

Confidence: 91% confidence
Finding: The deletion trigger phrase '第3条备忘完成了' is ambiguous because it describes task completion rather than explicitly requesting deletion. An agent could map ordinary conversational updates to a destructive action and remove notes without clear user consent, causing data loss or integrity issues.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: The skill documents deletion as a capability but does not warn that it is destructive or irreversible. Without a clear warning, users and calling agents may treat delete_memo as a routine operation and trigger irreversible removal of stored notes too casually.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal