msu-statusline-uninstall
Pass
Audited by Gen Agent Trust Hub on Sep 16, 2026
Risk Level: SAFECOMMAND_EXECUTIONDYNAMIC_EXECUTIONINDIRECT_PROMPT_INJECTIONDATA_EXFILTRATION
Full Analysis
- [COMMAND_EXECUTION]: The skill utilizes several shell utilities including
cp,mv,rm,rmdir, andjqto manage file operations and state transitions during the uninstallation process. It also invokes theclaudeCLI to programmatically uninstall the targeted plugin. - [DYNAMIC_EXECUTION]: In the verification step (step 5), the skill extracts a command string from the
settings.jsonfile and executes it usingbash -c. This pattern allows for the execution of arbitrary code defined within a configuration file. - [INDIRECT_PROMPT_INJECTION]: The skill ingests data from local configuration and backup files (
settings.jsonandmsu-statusline.prev) to restore the user's previous environment state. This data flows into the command execution path during verification. - Ingestion points: Reads from
settings.jsonandmsu-statusline.prevwithin the Claude configuration directory (defaulting to~/.claude). - Boundary markers: The skill does not employ delimiters or explicit safety instructions when handling the content of the restored command strings.
- Capability inventory: The skill possesses file write/delete permissions and the ability to spawn shell processes through
bash -c. - Sanitization: The skill performs a basic string check to ensure the restored command does not name the plugin being removed, but it lacks comprehensive validation or escaping for the shell commands it restores and executes.
- [DATA_EXPOSURE]: The skill accesses and modifies the
settings.jsonfile in the user's Claude configuration directory. This file contains global agent settings, plugin configurations, and potentially sensitive environment-specific metadata.
Audit Metadata