More screenshots
Works with the AI Agents you already use
Credential Leak Scan
A credential in a public repository is compromised the moment it is pushed, not the moment somebody notices.
Free
Credential Leak Scan
Example session with this skill installed
Check this repository before I push it to a public remote. I want to know if there are any real credentials in the working tree, and I do not want the secrets printed anywhere.
- Read your context and instructions
- Compiled the credential leak scan
Credential Leak Scan Report
Scanner: secret-leak-scan v1.0.0
Target: payments-api (working tree)
Files scanned: 12 | Findings: 10 | Files with findings: 5
Highest severity: critical | Rules fired: 10 of 10
The scan read every text file in the working tree and reported 10 findings across 5 files. The other 7 files were silent, which is the point: the scanner is not tuned to shout at ordinary code.
Findings
| Rule | Severity | File | Line | What it matched |
|---|---|---|---|---|
ENT-001 | critical | config/production.yml | 6 | Cloud access key identifier |
ENT-002 | critical | src/deploy.py | 4 | Source-hosting access token |
ENT-003 | critical | src/notifications.py | 3 | Messaging platform token |
ENT-004 | critical | src/deploy.py | 6 | Payment service secret key |
ENT-005 | critical | src/keys.py | 3 | Private key block |
ENT-006 | high | src/settings.py | 3 | Connection string with an inline credential |
ENT-007 | high | src/settings.py | 5 | Credential assigned to a literal value |
ENT-008 | medium | src/settings.py | 7 | High-entropy value under a credential-looking name |
ENT-009 | low | src/settings.py | 9 | Credential name still holds a placeholder value |
ENT-010 | low | src/settings.py | 11 | Credential name with an empty value |
Redacted evidence
| Rule | Evidence as emitted |
|---|---|
ENT-001 | value redacted at offset 82 |
ENT-002 | value redacted at offset 92 |
ENT-003 | value redacted at offset 57 |
ENT-004 | value redacted at offset 149 |
ENT-005 | value redacted at offset 93 |
ENT-006 | value redacted at offset 66 |
ENT-007 | api_key = Aq3F<redacted>4Nc9 |
ENT-008 | client_secret = Vx7Q<redacted>k0Lz (entropy 5.0 bits per character) |
ENT-009 | api_key = <placeholder> |
ENT-010 | webhook_secret = <empty> |
Severity breakdown
| Severity | Findings |
|---|---|
| critical | 5 |
| high | 2 |
| medium | 1 |
| low | 2 |
Recommendation
Treat the critical and high findings as rotation items, not cleanup items for later: a credential that has already been pushed is compromised the moment it reaches the remote, and deleting the line does not undo that. The low findings are a placeholder and an empty slot, which are worth fixing so the next reviewer is not misled and the one real key in the same file is not lost in the noise. Every finding carries a rule ID, a file and a line, and no credential is printed in full, so this report can be pasted into a ticket without leaking the secret a second time.
Next steps
- Rotate every critical and high finding at its issuer before you touch the tree.
- Read each reported file and line, then move the value to an environment variable or a secret manager.
- Confirm the low findings really are placeholders, then replace them with clearly invalid values.
- Run the scanner over the working tree before the first push, and add it to the pull request check.
- The scanner reads the working tree, not the commit history. If history is in scope, run a history-aware tool as well.
- Keep the scan in CI so a new leak is caught on the commit that introduced it.
Connects securely to your tools. The creator never sees your data.
About this skill
A credential in a public repository is compromised the moment it is pushed, not the moment somebody notices. The hard part is not finding the obvious token, it is telling a real key from a test value that looks like one, and doing it without pasting the secret into a chat or a ticket.
This skill scans a repository or a folder for leaked credentials and reports what it found with the value redacted. It combines exact-pattern detection for known provider token shapes, Shannon entropy scoring for high-entropy strings that no pattern covers, and a placeholder recogniser so that sample values and environment variable names are not reported as incidents.
Every finding carries a rule identifier, a severity, a file and a line. No credential value is ever printed in full. A credential assigned to a literal value keeps the first four and last four characters with the middle replaced, a known provider shape is reported only by the offset where it matched, and a placeholder or an empty slot is reported as a marker. A reviewer can confirm the match from the rule ID, the file and the line without the secret being copied anywhere. Findings are grouped into severity bands, so the output goes straight into a backlog.
It is a static scan of the working tree. It does not read the commit history, it does not verify a credential against a live provider, and it does not promise to find everything. It is fast, deterministic, private and good at the large majority of what actually leaks.
Offline scan only. No history scanning or live issuer verification. Pattern matching is limited to the ten provided rules. Entropy checks require credential-like names to trigger.
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 any payment.
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
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 4 days ago
- Free with an Agensi account
Requires
Permissions
File Scopes
Terminal / Shell is used to run the bundled scanner. Read Files is used to read the repository or folder you want checked. The scanner only reads: it never writes to your tree, never opens a browser and never makes a network request. It reads the working tree, not the commit history.