cline-runner
Pass
Audited by Gen Agent Trust Hub on Sep 8, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONPERSISTENCEEXTERNAL_DOWNLOADS
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill aggregates data from several untrusted sources to construct a final prompt for the Cline agent, which has autonomous capabilities like shell and filesystem access.
- Ingestion points: Untrusted data enters the agent context through the positional
promptargument, as well as the--prompt-file,--session-file, and--metadata-jsonflags processed inscripts/run_cline.py. - Boundary markers: The
build_promptfunction inscripts/run_cline.pyuses plain text delimiters (e.g., "Execution metadata:", "Prior conversation context to continue from:") to separate sections. These are not robust against adversarial content designed to break out of delimiters. - Capability inventory: The skill executes the Cline CLI, which possesses capabilities for reading and writing files, and executing arbitrary shell commands, particularly when not restricted to 'plan' mode.
- Sanitization: No escaping, validation, or filtering of the external content is performed before it is interpolated into the final prompt.
- [COMMAND_EXECUTION]: The skill uses the
subprocess.runfunction to execute theclinebinary. It correctly follows security best practices by passing arguments as a list rather than a shell string, preventing direct command injection into the wrapper itself. - [PERSISTENCE]: Invoking the skill with the
--modelflag causes a persistent side effect on the host system by overwriting the user's global Cline configuration file (~/.cline/data/settings/providers.json). While documented, this changes the behavior of subsequent interactive Cline sessions. - [EXTERNAL_DOWNLOADS]: The documentation identifies the
clineCLI as a mandatory prerequisite, directing users to install it via a remote registry usingnpm install -g cline.
Audit Metadata