diagnosing-superpowers

Pass

Audited by Gen Agent Trust Hub on Oct 22, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONDATA_EXFILTRATION
Full Analysis
  • [INDIRECT_PROMPT_INJECTION]: The skill processes untrusted session transcripts which could theoretically contain malicious instructions designed to influence the agent.\n
  • Ingestion points: SKILL.md step 2 locates session files, and analyst subagents defined in prompts/analyst-common.md read these files for triage.\n
  • Boundary markers: Instructions in prompts/analyst-common.md strictly scope the subagent's role to reporting findings with evidence, explicitly forbidding them from fixing code or modifying session files.\n
  • Capability inventory: The main agent possesses file system access for reading transcripts and creating bundles, shell access for analysis tools (awk, jq, sed), and network access for GitHub integration via the gh tool and curl.\n
  • Sanitization: The skill implements a formal data sanitization workflow in prompts/scrub.md and prompts/scrub-audit.md, governed by a detailed references/redaction-policy.md. This ensures sensitive data like secrets and PII are replaced with placeholders before export.\n- [COMMAND_EXECUTION]: The skill utilizes standard system utilities to perform file analysis and manage diagnostic bundles.\n
  • Evidence: references/context-safety.md uses wc, awk, grep, jq, and sed to safely inspect large transcript files. SKILL.md utilizes zip or tar for bundle creation.\n
  • Context: These tools are used locally to process data and do not incorporate unvalidated external input into executable command strings. Findings from these tools are cited with path:line evidence.\n- [DATA_EXFILTRATION]: The skill provides functionality to share diagnostic information via GitHub issues or compressed bundles.\n
  • Evidence: SKILL.md steps 5 and 6 describe the process for filing GitHub issues and exporting session bundles.\n
  • Mitigation: The skill includes extensive safeguards: a multi-stage scrubbing process, a dedicated privacy audit step, and a strict requirement for human partner approval of both the exact text of GitHub issues and the contents of any archive before transmission. GitHub interactions target the author's repository obra/superpowers.
Audit Metadata
Risk Level
SAFE
Analyzed
Oct 22, 2026, 08:27 PM