secrets pattern scanner
Scan files for API keys, tokens and private keys offline (gitleaks-style). AWS, GitHub/GitLab PATs, Slack, Stripe, Google, npm/PyPI, JWTs and PEM keys — values redacted.
$8
Works with the AI Agents you already use
secrets pattern scanner
Example session with this skill installed
Scan the current directory for any committed API keys or Slack tokens and give me a Markdown report.
- Read your context and instructions
- Compiled the secrets pattern scanner
I have scanned the local directory for hardcoded credentials. The scanner identified 3 high-risk findings across your configuration and source files. All values in the report below have been redacted to prevent further exposure.
Secrets Scan Results
| File Path | Type | Risk Level | Pattern Match (Redacted) |
|---|---|---|---|
config/services.yaml | AWS Access Key | CRITICAL | AKIA...[REDACTED] |
.env.development | Slack Bot Token | HIGH | xoxb-...[REDACTED] |
src/auth/helper.py | Private Key (PEM) | HIGH | -----BEGIN RSA...[REDACTED] |
Remediation Steps Required:
1.
Rotate Credentials: The AWS Access Key and Slack Bot Token must be revoked and re-issued immediately through their respective provider consoles.
2.
Scrub History: Since these were found in the file tree, use git filter-repo or BFG Repo-Cleaner to remove these strings from all historical commits.
3.
Environment Variables: Move the Slack token from .env.development to a secure vault or encrypted environment variable store.
Next steps
- Run
jwt token risk analyzerto inspect the scope of the found JWTs. - Use
github actions workflow auditorto check if these secrets are being logged in CI. - Add false positives to your allowlist or use
# secretscanner:allowfor verified mocks.
Connects securely to your tools. The creator never sees your data.
About this skill
Find committed API keys and private keys before attackers do — values stay redacted.
A single leaked ghp_ or AKIA key is enough. This skill walks a file or directory with gitleaks-style patterns for AWS keys, GitHub/GitLab PATs, Slack tokens/webhooks, Stripe live keys, Google API keys, npm/PyPI tokens, JWTs and PEM private keys. Reports redact the secret values.
What it does
- Skips
.git,node_modules, binaries and common lock/build dirs - Allowlist file or
# secretscanner:allowper line for false positives - Markdown + CSV; exit 0 when clean
Who it's for
Developers and security engineers scanning a repo checkout or a suspicious .env before it ships.
Limits
Regex heuristics — expect some false positives; always rotate anything real and scrub git history. Not legal advice.
What's included
SKILL.md: workflow, commands, how to explain findingsscripts/: the checker (stdlib Python) plus sharedseccommon.pyreferences/sources.md: specs and guidance citedexamples/: good and bad samples used in the demotests/: unit tests (Python 3.8 / 3.9 / 3.13)
Standard-library Python only. No API keys, no network calls, no installs.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
- Offline / local files only — does not fetch live URLs or call cloud APIs.
- Heuristic checks; not a full substitute for a professional audit or pentest.
- Not legal advice and not a certification of compliance.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 20 days ago
Permissions
File Scopes
Fully offline. No subprocess, no network modules used for outbound calls, no credential access.