shieldcortex@5.20.2
VERIFIED· install onlyPublisher claims: "Memory and defence for AI agents: semantic recall, knowledge graph and decay, plus a memory firewall that scans and enforces against prompt injection, credential leaks and poisoning." 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
What changed since 5.20.0
vet-skills diff shieldcortex 5.20.0 5.20.2In the sandbox, this version reached for nothing 5.20.0 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-18 and scored it 84/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
…ry or conversation content. `actionGuard.packageVetting.enabled false` in config.json always stops the watch's lookups, policy lock or not, because the watch reads config.json as written; it stops the tool-call lookups only on a host witho…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.- $CWD/.env (env-scanner checks for leaked secrets — reads, never writes)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- **Not uploaded by default:** local agent configs, MCP configs, raw rules files, shell configs, SSH keys, secrets, `.env` contents, or arbitrary project files.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…d, but with no separate host allowlist; and the OpenClaw `cortex-memory` hook's npx package resolution (`npx mcporter`, and `npx -y shieldcortex` when no accessible `binar…Fix: Pin versions and sources; vendor anything fetched at install time.… updates and X-Ray package lookups, and the OpenClaw `cortex-memory` hook's npx package resolution (`npx mcporter`, and `npx -y shieldcortex` when no accessible `binar…Fix: Pin versions and sources; vendor anything fetched at install time.- **Environment** — .env files for leaked credentials (read-only check, never writes)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…alse` stops it, policy lock or not (the watch reads `enabled: false` from config.json as written). That is the watch only: under a verified or unverifiable policy lock or the strict fail-closed posture, `enabled: false` is dropped for the …Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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.