ClawAudit verdict

android-remote-browser-debug

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

Uses ADB port forwarding and Chrome DevTools Protocol over localhost to debug an Android browser connected via USB; all traffic is local (localhost:9222) and the JavaScript execution is for legitimate debugging of the developer's own device.

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

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

0
security
50
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Performs file operations but does not declare file-accessing binaries

file_read+write

Findings (4)

Pattern match critical

Pipe-to-python pattern — remote code execution risk

SKILL.md · code · curl -s http://localhost:9222/json/list | python

Pattern match critical

Pipe to python — executes piped content as Python code

SKILL.md · code · | python3

Pattern match medium

Opens WebSocket connection

SKILL.md · code · WebSocket

Pattern match medium

Node http/https module — low-level network access

SKILL.md · code · require('http')

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class C). 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.

network_outfile_writedata_encoding

Is this flag fair?

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