Secrets Scan
Find leaked credentials in files: high-signal provider patterns (AWS/GitHub/Slack/Google/Stripe/OpenAI/SendGrid/Twilio/JWT/PEM private keys) plus a generic high-entropy secret-assignment catch with placeholder filtering. Matches are REDACTED in output — never echoes a full secret. Pure stdlib, read-only.
Install
$ agentstack add skill-batteryshark-rekit-secrets-scan ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-batteryshark-rekit-secrets-scan) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Secrets Scanner
Find leaked credentials — API keys, tokens, private keys — in a file or a whole tree. Pure-stdlib, read-only, and it redacts every match (never echoes a full secret).
When to use
Checking whether a package, dump, or repo you're analysing carries hard-coded credentials — either an attacker's exfil target or a victim's leaked keys. Run it on source, configs, .env, and extracted archives.
What it finds
- Provider patterns (high confidence): AWS access keys, GitHub tokens/PATs, Slack
tokens & webhooks, Google API keys, Stripe keys, OpenAI keys, npm/PyPI tokens, SendGrid, Twilio, JWTs, and PEM PRIVATE KEY blocks.
- Generic (entropy-gated):
api_key = "…"/password: "…"style assignments
whose value is high-entropy and not an obvious placeholder (changeme, ${VAR}, your_key_here, …) → SECRET.GENERIC_HIGH_ENTROPY.
Every value is redacted to prefix…suffix [N chars]; private keys are reported as presence only. It never validates a key against a live service — no network, ever.
Usage
rekit run secrets-scan ./package
rekit run secrets-scan ./.env --format json
rekit run secrets-scan ./src --min-entropy 3.5 # stricter generic gatePrerequisites
- python3 ≥ 3.8 — pure stdlib, nothing to vendor.
Note
Regex/entropy heuristics find candidates, not proof — confirm before acting, and remember a real find means the key should be rotated.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/rekit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.