Caveat verdict

trace-debugger-safety

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

The skill seems to be designed with safety in mind, treating untrusted logs as potential prompt-injection inputs, truncating and sanitizing logs, and making Codex analysis optional.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

68
security
90
transparency
70
maintenance

Findings (3)

Pattern match high

HTTP request to bare IP address — common in malicious payloads

SKILL.md · code · http://127.0.0.1

Pattern match medium

subprocess execution — runs system commands from Python

scripts/trace_debugger_safety.py · prose · downgraded · subprocess.run(

Pattern match low

Python urllib.request — network access

scripts/trace_debugger_safety.py · prose · downgraded · urllib.request

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API