context-verifier@1.5.1
VERIFIED· install onlyPublisher claims: "Know the file you're editing is the file you think it is — verify integrity before you act" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-21 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
| Secrets written to disk | Never use `--include-content` with `.env`, credentials, or secret files |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.| minor | `*.log`, `*.tmp`, `output/*` | Info only |Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.> Never use this flag with sensitive files (`.env`, credentials, secrets).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./cv packet .env --include-content # Stores secrets to disk!Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.| critical | `*.env`, `*credentials*`, `*secret*`, project config | Block operation |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.The `critical_patterns` (e.g., `*.env`, `*credentials*`, `*secret*`) are used for:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
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.