trader-explain
Warn
Audited by Gen Agent Trust Hub on Jun 13, 2026
Risk Level: MEDIUMCOMMAND_EXECUTIONCREDENTIALS_UNSAFEPROMPT_INJECTIONEXTERNAL_DOWNLOADS
Full Analysis
- [COMMAND_EXECUTION]: Step 2 executes a shell command
npx neural-trader --predict --signal "$SIGNAL_ID" --explain --json. The variable$SIGNAL_IDis sourced from thesignalIdargument provided by the user. If this input is not strictly validated to be alphanumeric, an attacker can perform command injection (e.g., by passing; curl ...) to execute arbitrary code in the host environment. - [CREDENTIALS_UNSAFE]: Step 6 specifies a workflow to resolve a private signing key from the local filesystem at
verification/witness-key.jsonor via theRUFLO_WITNESS_KEY_PATHenvironment variable. Accessing raw private keys (Ed25519) directly within a skill's logic increases the risk of credential exposure if the skill's execution context is compromised. - [PROMPT_INJECTION]: The skill is vulnerable to indirect prompt injection (Category 8) as it ingests and processes untrusted data from the
trading-signalsmemory namespace. - Ingestion points: Step 1 retrieves signal data including
modelId,prediction, andfeaturesfrom thetrading-signalsnamespace. - Boundary markers: No delimiters or instructions are used to distinguish between system instructions and data retrieved from memory.
- Capability inventory: The skill possesses significant capabilities including shell command execution (
bashin Step 2) and persistence to long-lived memory (mcp__claude-flow__memory_storein Step 7). - Sanitization: There is no evidence of sanitization or escaping for the
featuresmetadata orSIGNAL_IDbefore they are interpolated into the final markdown report or the bash command line. - [EXTERNAL_DOWNLOADS]: The skill uses
npx neural-trader, which downloads and executes theneural-traderpackage from the npm registry at runtime. While this appears to be a resource associated with the author's ecosystem (ruvnet/ruflo), it represents an external dependency download.
Audit Metadata