Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md ### CLI Usage (scripts/executor.ts)
Security audit
Security checks for vulnerabilities and agentic risk
This skill openly runs multiple agent tasks in parallel, but its broad activation and unbounded task dispatch deserve user review before installation.
Install only if you deliberately want a skill that can fan out multiple agent sessions. Use it with explicit task lists, low concurrency, and trusted inputs; avoid giving it broad file-write, account-changing, or public-posting tasks unless you are prepared to review the effects of each spawned session.
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
Referenced artifact was not completely inspected
### CLI Usage (scripts/executor.ts)
The README explicitly promotes batch file operations including read/write in parallel but does not warn about the risk of concurrent data modification, overwrites, race conditions, or accidental destructive changes. In the context of a parallel-execution skill, missing safety guidance is more dangerous because simultaneous writes can amplify mistakes and make recovery harder.
The trigger description uses broad natural-language phrases such as 'run these in parallel' and 'concurrent tasks', which can match ordinary user intent too loosely and cause the skill to activate unexpectedly. In an agent environment, over-broad activation can route benign requests into a high-capability skill that spawns multiple operations at once, increasing the chance of unintended actions, resource overuse, or unsafe parallel execution.
The skill documents process-spawning behavior and interaction with the Hermes CLI, but it declares no explicit tool scope or permissions boundaries. In an agent environment, missing scope metadata can allow the skill to be invoked with broader-than-expected capabilities, increasing the chance of unintended command execution or environment access.
The description uses broad natural-language triggers such as 'run these in parallel' and 'concurrent tasks,' which are common phrases that may appear in ordinary user requests. This can cause accidental activation of a skill that spawns multiple subprocess-like sessions, magnifying the effect of a mistaken invocation and potentially launching tasks the user did not explicitly authorize.
The 'When to Use' section defines activation conditions with ambiguous phrases like 'user wants faster results' and 'multiple independent tasks need to be executed at once,' which are subjective and easy to over-match. Because this skill can initiate concurrent task execution, ambiguous routing increases the risk of unnecessary parallel runs, resource exhaustion, or execution of unintended actions.
The executor forwards task.description directly to an external agent CLI (hermes cli with sessions_spawn), causing arbitrary user-supplied content to be transmitted for downstream execution without any confirmation, warning, or trust boundary enforcement. In the context of a parallel-execution skill, this increases the chance that sensitive instructions, secrets, or destructive task requests are fanned out to multiple subprocesses at once, amplifying impact if the input is unsafe or attacker-controlled.
Detected: suspicious.dangerous_exec