T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party CLI Installation and Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent memories.sh CLI guide, but its cloud-sync and forced-restore workflows can upload or overwrite broad AI-agent configuration without enough safeguards or warnings.
Review this skill carefully before installing. Prefer a pinned or locally locked CLI version, avoid syncing global/project config directories until you have inspected exactly what will be uploaded, use dry-run/diff/list/show commands first, back up existing AI tool configs before any apply operation, and avoid force-restoring cloud-synced instruction files unless you trust the account and snapshot source.
SKILL.md:16Unpinned Third-Party CLI Installation and Execution
references/workflows.md:66Broad Upload of Global and Project AI Configuration to a Cloud Service
references/workflows.md:73Forced Cloud Restoration Can Persist Poisoned Agent Instructions
The skill recommends executing npx @memories.sh/cli without pinning a specific package version, which allows the fetched code to vary over time and exposes users to supply-chain risk if a malicious or compromised release is published. In a security-sensitive agent skill, this is especially risky because users may copy-paste the command directly and execute remote code immediately.
The cloud sync and file restoration workflow includes actions like syncing local data, uploading config files, and force-applying global configs, but it does not warn about overwriting local settings, propagating sensitive data, or changing agent/tool behavior across environments. Because this skill is operational guidance for a CLI that manages persistent memory and agent configuration, omission of impact warnings can lead users to perform destructive or privacy-affecting actions without informed consent.
The semantic search and embedding features are described without warning that memory content may be sent to an embedding provider or external model endpoint. Since memories may contain proprietary or secret data, hidden transmission to an embedding service creates a privacy and data-handling risk.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**Options:**
- `--hard` — Permanent deletion
- `-f, --force` — Skip confirmation
### `memories tag <id> <action> [tags]`
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**Options:**
- `--dry-run` — Preview without writing
- `-f, --force` — Overwrite without confirmation
**Output Paths:**
| Target | File |
The memories sync command documents cloud synchronization but does not warn users that local memory contents may be transmitted to a remote service. Because this tool handles persistent agent memories that may contain sensitive project data, users could unknowingly exfiltrate code, notes, secrets, or internal instructions to the cloud.
The workflow instructs users to restore global configuration files with a force flag, which can overwrite local user settings without prompting or emphasizing the risk. In a skill specifically used to manage AI tool configs across machines, this is materially dangerous because users may unintentionally replace machine-specific or security-relevant local configuration, causing loss of settings or propagation of unsafe configs.
The workflow recommends exporting rules and decisions to YAML and committing them to git without warning that these files may contain sensitive operational facts, internal decisions, or secrets copied into memory entries. In this skill context, memories are a persistent knowledge layer and are likely to store high-value project context, so encouraging direct versioning increases the chance of accidental data exposure.
The authentication documentation explains login/logout behavior but does not disclose that auth credentials or tokens will be stored locally. Users operating on shared machines or regulated environments may make unsafe assumptions about credential persistence and local exposure.