
Credential Scanner
- 500 installs
- 70 repo stars
- Updated March 10, 2026
- useai-pro/openclaw-skills-security
credential-scanner is a workspace secret-scanning skill that detects exposed API keys and tokens for developers who need a pre-flight check before OpenClaw skills read project files.
About
credential-scanner is a security skill from useai-pro/openclaw-skills-security that scans a workspace for exposed credentials, API keys, tokens, and private key patterns before any OpenClaw skill receives file-read access. The module uses path-aware regex checks, skip rules, and sanitized reporting that lists findings with masked output instead of printing raw secrets. Metadata states the goal is reducing accidental credential exposure when untrusted or newly added skills inspect the filesystem. A developer reaches for credential-scanner immediately before enabling agent skills on repositories that may contain .env files, cloud keys, or JWT signing material.
- credential-scanner
Credential Scanner by the numbers
- 500 all-time installs (skills.sh)
- +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #822 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/useai-pro/openclaw-skills-security --skill credential-scannerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 500 |
|---|---|
| repo stars | ★ 70 |
| Last updated | March 10, 2026 |
| Repository | useai-pro/openclaw-skills-security ↗ |
How do you scan a repo for exposed secrets before agents run?
Use credential-scanner for development tasks
Who is it for?
Developers enabling OpenClaw or other file-reading agent skills who need a fast pre-flight secret scan with masked output.
Skip if: Teams needing full SAST, dependency CVE scanning, or production runtime secret rotation should use dedicated security platforms instead of credential-scanner alone.
When should I use this skill?
Before any OpenClaw skill gets filesystem access or when a user asks to scan for exposed API keys and tokens in a project.
What you get
Masked credential findings list, skipped-path report, and sanitized cleanup guidance without raw secret values.
- masked findings report
- cleanup guidance
Files
Credential Scanner
You are a credential scanner for OpenClaw projects. Before the user runs any skill that has fileRead access, scan the workspace for exposed secrets that could be read and potentially exfiltrated.
What to Scan
High-Priority Files
Default scope: current workspace only. Scan project-level files first:
.env,.env.local,.env.production,.env.*docker-compose.yml(environment sections)config.json,settings.json,secrets.json*.pem,*.key,*.p12,*.pfx
Home directory files (scan only with explicit user consent):
~/.aws/credentials,~/.aws/config~/.ssh/id_rsa,~/.ssh/id_ed25519,~/.ssh/config~/.netrc,~/.npmrc,~/.pypirc
Patterns to Detect
Scan all text files for these patterns:
# API Keys
AKIA[0-9A-Z]{16} # AWS Access Key
sk-[a-zA-Z0-9]{48} # OpenAI API Key
sk-ant-[a-zA-Z0-9-]{80,} # Anthropic API Key
ghp_[a-zA-Z0-9]{36} # GitHub Personal Token
gho_[a-zA-Z0-9]{36} # GitHub OAuth Token
glpat-[a-zA-Z0-9-_]{20} # GitLab Personal Token
xoxb-[0-9]{10,}-[a-zA-Z0-9]{24} # Slack Bot Token
SG\.[a-zA-Z0-9-_]{22}\.[a-zA-Z0-9-_]{43} # SendGrid API Key
# Private Keys
-----BEGIN (RSA |EC |DSA |OPENSSH )?PRIVATE KEY-----
-----BEGIN PGP PRIVATE KEY BLOCK-----
# Database URLs
(postgres|mysql|mongodb)://[^\s'"]+:[^\s'"]+@
# Generic Secrets
(password|secret|token|api_key|apikey)\s*[:=]\s*['"][^\s'"]{8,}['"]Files to Skip
Do not scan:
node_modules/,vendor/,.git/,dist/,build/- Binary files (images, compiled code, archives)
- Lock files (
package-lock.json,yarn.lock,pnpm-lock.yaml) - Test fixtures clearly marked as examples (
example,test,mock,fixturein path)
Output Format
CREDENTIAL SCAN REPORT
======================
Project: <directory>
Files scanned: <count>
Secrets found: <count>
[CRITICAL] .env:3
Type: API Key (OpenAI)
Value: sk-proj-...████████████
Action: Move to secret manager, add .env to .gitignore
[CRITICAL] src/config.ts:15
Type: Database URL with credentials
Value: postgres://admin:████████@db.example.com/prod
Action: Use environment variable instead
[WARNING] docker-compose.yml:22
Type: Hardcoded password in environment
Value: POSTGRES_PASSWORD=████████
Action: Use Docker secrets or .env file
RECOMMENDATIONS:
1. Add .env to .gitignore (if not already)
2. Rotate any exposed keys immediately
3. Consider using a secret manager (e.g., 1Password CLI, Vault, Doppler)Rules
1. Never display full secret values — always truncate with ████████ 2. Check .gitignore and warn if sensitive files are NOT ignored 3. Differentiate between committed secrets (critical) and local-only files (warning) 4. If running before a skill with network access — escalate all findings to CRITICAL 5. Suggest specific remediation for each finding 6. Check if the project has a .env.example that accidentally contains real values
Related skills
FAQ
When should credential-scanner run?
credential-scanner should run before OpenClaw skills receive file-read access, scanning the workspace to reduce accidental credential exfiltration by untrusted or new skills.
Does credential-scanner print raw secrets?
credential-scanner uses sanitized reporting with masked output and skip rules so findings are listed without echoing full API keys or tokens.
What patterns does credential-scanner detect?
credential-scanner matches common API keys, tokens, and private key patterns via path-aware regex checks across the project workspace.