trace

Fail

Audited by Snyk on Apr 21, 2026

Risk Level: CRITICAL
Full Analysis

CRITICAL E006: Malicious code pattern detected in skill scripts.

  • Malicious code pattern detected (high risk: 0.90). The skill intentionally mines local session files and repository metadata, writes trace logs into project repos, and calls external "Oracle"/arra_trace APIs—behavior that can exfiltrate sensitive conversation content and repo data to a centralized service.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 0.90). The skill explicitly clones arbitrary repository URLs into ghq ("With --repo [url]: Clone to ghq first" / "ghq get -u "$URL"") and in deep mode runs GitHub queries for issues/PRs ("Agent E: GitHub Issues/PRs" using gh issue list --search) and then reads and interprets those repo files, commit history, and PR/issue data as part of its required trace workflow, meaning it consumes untrusted, user-generated third‑party content that can materially influence its search/escalation and logging actions.

Issues (2)

E006
CRITICAL

Malicious code pattern detected in skill scripts.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

Audit Metadata
Risk Level
CRITICAL
Analyzed
Apr 21, 2026, 07:18 AM
Issues
2