systematic-debugging@r1

CAUTION

Publisher claims: "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry skills.shPublisher obra · joined 2 days agoInstalls 305KLast detonated 33 h ago

Dispute verdict

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations

t+CategoryObserved action

0.0sprocessno install scripts in bundle

0.0sprocessscript backend runs setup only

Static findings

CRITICAL

Access to sensitive file pathsroot-cause-tracing.md:77 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files

AST05

CRITICAL

Access to sensitive file pathsdefense-in-depth.md:58 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files

AST05