key-guard@1.0.1
VERIFIED· install onlyPublisher claims: "Security guardrail: prevents API keys from being sent to Claude. Triggers when user asks to call an external API, use a key, check credentials, read .env fil..." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 1 of 1 bundled script run with no arguments, with decoy credentials in the environment · 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 (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 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 · 2 scenarios · 0 deviationsStatic findings
// Priority: shell profiles (lowest) → .env → process.env (highest)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. **NEVER read `.env` or key files directly** — do not use bash `cat .env` or file read tools on any file containing keysFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* Reads API keys from .env file LOCALLY and exposes tools that ClaudeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…gers when user asks to call an external API, use a key, check credentials, read .env files, or view/edit scripts that may contain hardcoded keys. Always routes key …Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Copy .env.example to .env and fill in your keysFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Read `.env`, `*.key`, `secrets.*`, or any credentials fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const ENV_FILE = path.resolve(__dirname, ".env");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Shell profile files to scan for KG_* keys, in priority order (last wins before .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.description: "List all available key names from .env and shell profiles. Returns only names — never values.",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.