agent-store-cli@0.1.1
VERIFIED· install onlyPublisher claims: "Agent Store deployment CLI for local coding agents." 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 0.1.0
vet-skills diff agent-store-cli 0.1.0 0.1.1This version reaches for something 0.1.0 did not: 1 new host (guanxintec.com). Compared from the two recorded runs, not from source.
- New hosts
- guanxintec.com
0.1.0 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
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-20 and scored it 86/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
if (name === '.env' || name.startsWith('.env.'))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (flags.json || !input.isTTY) {Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.if (flags.json || flags.yes || !input.isTTY) {Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.- Never read or print `.env` secrets unless the user explicitly asks and it is necessary.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (flags.json || flags.yes || !input.isTTY)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
Not checked against OSV yet; the weekly check has not reached this version.