Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local clustering tool that stores and exports clustering runs in ways that are disclosed and aligned with its purpose, though users should be careful with saved dataset metadata and export paths.
Install only if you are comfortable with clustering results and source input paths being saved locally in ~/.cluster. Avoid using it on highly sensitive datasets unless local retention is acceptable, and be careful when setting OUTPUT because an existing file at that path can be overwritten.
The export command writes to an arbitrary path supplied via the OUTPUT environment variable with open(output, "w"), allowing overwrite of any file the current user can access. In an agent setting, this can be abused to clobber shell profiles, application configs, or other sensitive files outside the skill's data directory.
The skill describes command execution that reads environment variables and persistently writes clustering results and configuration under the user's home directory, but it declares no explicit tool scope or permissions. That mismatch can cause users or orchestration systems to grant broader access than expected and makes the skill's file-write behavior less transparent, increasing the risk of unintended data exposure or modification.
The skill persists clustering run data, including source input file paths, parameters, assignments, centroids, and metrics, in ~/.cluster/data.jsonl, but the high-level description does not warn users about that persistent local storage. In a data-analysis context, this is especially risky because clustering inputs and outputs may contain sensitive or proprietary dataset information that users may assume is processed ephemerally.
Automatic session persistence is present through creation of ~/.cluster and durable storage of run history/configuration. In this skill context, persistent retention is more dangerous because clustering commonly operates on user datasets whose metadata and derived results may be sensitive and need not be kept after execution.
CONFIG_FILE="$DATA_DIR/config.json"
VERSION="1.0.0"
mkdir -p "$DATA_DIR"
touch "$DATA_FILE"
if [ ! -f "$CONFIG_FILE" ]; then
The skill automatically creates and uses persistent storage under ~/.cluster for run history and configuration, even though the manifest only describes clustering analysis. This expands the skill from one-shot analysis into local state management, which can retain sensitive input-derived metadata and surprise users who did not expect persistence.
The script silently persists run data and configuration under ~/.cluster without warning the user that input-derived details, file paths, metrics, assignments, and centroids will be stored. This creates privacy and data-retention risk, especially when clustering sensitive datasets.
The script includes broad import/export, configuration, listing, and statistics features that go beyond the stated purpose of performing clustering analysis. These extra data-management capabilities increase attack surface and enable handling of arbitrary local files and retained records unrelated to core clustering.
The export path is used directly and existing files are overwritten without confirmation, backup, or visibility into the target location. This can lead to destructive data loss or unintended modification of user files even without a sophisticated exploit.
The config command permits arbitrary key/value writes to a persistent JSON configuration file, not just a fixed safe schema for clustering parameters. While the current script consumes only a few settings, this pattern enables unbounded local state manipulation beyond core execution and can become risky as the tool evolves or if other components trust that file.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
if not runs:
print("No clustering runs found.")
print("Use 'run' command to create a new clustering run.")
sys.exit(0)
if sort_by == "k":
The config command persistently modifies ~/.cluster/config.json without disclosing that the change is durable or documented in help output. This is primarily a transparency and user-expectation problem that can cause confusing behavior across future runs.
No suspicious patterns detected.