cavecrew@r2

VERIFIED

Publisher claims: "When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer. " Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry skills.shPublisher juliusbrussee · joined 16 days agoInstalls 372KLast detonated 2 h ago

$npx skills add cavecrew

Watch Report an issue

Is cavecrew@r2 safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-11-06 and scored it 93/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

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

0.0sprocessno install scripts to re-run

Static findings

No findings across 79 lines in 1 files.

Cost to the agent

Instructions loaded

≈998 tok

1 file · 1 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.