statusline-setup

Warn

Audited by Gen Agent Trust Hub on Oct 11, 2026

Risk Level: MEDIUMREMOTE_CODE_EXECUTIONCOMMAND_EXECUTIONEXTERNAL_DOWNLOADSDYNAMIC_EXECUTIONPRIVILEGE_ESCALATIONINDIRECT_PROMPT_INJECTION
Full Analysis
  • [REMOTE_CODE_EXECUTION]: The skill facilitates the installation of the third-party tool 'ccstatusline' using bunx ccstatusline@latest or npx ccstatusline@latest. This executes code fetched directly from the npm registry without version pinning or integrity verification, which could lead to the execution of malicious code if the package is compromised.
  • [COMMAND_EXECUTION]: The skill generates shell scripts (e.g., statusline.sh) and configures the agent to execute them as part of its UI loop. The installation script scripts/install-statusline.sh automates this process and performs multiple shell operations including git commands and JSON parsing.
  • [EXTERNAL_DOWNLOADS]: The skill downloads the ccstatusline package from the npm registry and references external GitHub repositories such as github.com/sirmalloc/ccstatusline and github.com/Piebald-AI/tweakcc for additional functionality.
  • [DYNAMIC_EXECUTION]: The agent is configured to dynamically execute shell commands and scripts at runtime for status line updates (at an interval of approximately every 300ms). It also utilizes bunx for on-the-fly execution of remote packages.
  • [PRIVILEGE_ESCALATION]: The scripts/install-statusline.sh script applies chmod +x to dynamically created shell scripts in the user's home directory. This grants execution permissions to content generated during the setup process.
  • [INDIRECT_PROMPT_INJECTION]: The skill ingests untrusted data from the workspace and session history to display in the status line. In the examples/peacock-statusline.sh script, values read from .vscode/settings.json are interpolated directly into an awk command string without validation, creating a potential command injection surface.
  • Ingestion points: Session transcript JSON file (transcript_path) and workspace configuration (.vscode/settings.json).
  • Boundary markers: None present in the provided scripts or instructions.
  • Capability inventory: The skill uses Bash, git commands, awk, and jq to process data and update the terminal interface.
  • Sanitization: While some fields are handled via jq, the peacock-statusline.sh script lacks adequate validation for color strings and transcript data before use in shell commands.
Audit Metadata
Risk Level
MEDIUM
Analyzed
Oct 11, 2026, 07:04 PM