qcsd-refinement-swarm
Warn
Audited by Gen Agent Trust Hub on Sep 18, 2026
Risk Level: MEDIUMCOMMAND_EXECUTIONDYNAMIC_EXECUTIONINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADS
Full Analysis
- [COMMAND_EXECUTION]: The skill relies on external command-line utilities (
aqeandruflo) for critical operations like memory retrieval and state persistence.\n - Evidence:
steps/01-flag-detection.mdexecutesaqe memory searchandnpx --no-install ruflo memory search.\n - Evidence:
steps/07-learning-persistence.mdexecutesaqe memory storeandaqe memory share.\n- [DYNAMIC_EXECUTION]: Shell command templates within the skill use string interpolation to inject variables, which is a known pattern for command injection vulnerabilities if the variables contain user-controlled content.\n - Evidence:
steps/07-learning-persistence.mdconstructs a shell command using--key \"qcsd-refinement-${storyId}-${Date.now()}\"and a JSON--valuestring, both of which are susceptible to shell escaping and injection.\n- [INDIRECT_PROMPT_INJECTION]: The skill is designed to ingest and analyze untrustedSTORY_CONTENTto gate its execution logic via flags (e.g.,HAS_API), creating a risk that instructions inside the data could manipulate the swarm's behavior.\n - Ingestion points: The
STORY_CONTENTprovided by the user is processed insteps/01-flag-detection.md.\n - Boundary markers: No delimiters or specific instructions are provided to the agent to prevent it from obeying instructions embedded within the user story text.\n
- Capability inventory: The skill has access to shell execution tools (
aqe,ruflo), can write multiple files to the filesystem (OUTPUT_FOLDER), and can spawn various sub-agents with differing capabilities.\n - Sanitization: There is no evidence of input sanitization or validation performed on the story content before it is used for logic branching or stored in persistence layers.\n- [EXTERNAL_DOWNLOADS]: The skill introduces a dependency on the Node.js package
ruflovianpx.\n - Evidence:
steps/01-flag-detection.mdreferencesruflo, which is an uncommon/unverified package. While usage via--no-installmitigates immediate remote downloads, it remains an unverifiable dependency.
Audit Metadata