whatileaked
Find Credentials Leaked in AI Coding Histories
AI coding histories can retain credentials after they were shared with a model provider. This skill finds affected records while keeping reported secrets masked.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "whatileaked" from https://skillstore.io/skills/selan-ai-whatileaked.md and its manifest at https://skillstore.io/api/skills/selan-ai-whatileaked/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "whatileaked". Scan my coding-agent histories for leaked credentials.
Expected outcome:
The scan found two fingerprints across three files. Rotate the likely production credential before considering local cleanup.
Using "whatileaked". Are these two findings the same credential?
Expected outcome:
Yes. The matching fingerprint indicates one credential appeared in both locations, although the secret itself remains masked.
Using "whatileaked". Help me interpret a masked test-key finding.
Expected outcome:
- The context suggests a test fixture rather than an active credential.
- Confirm the source file and deployment use before dismissing it.
- Rotate the credential if its status remains uncertain.
Security Audit
High RiskAll four static findings are false positives caused by Markdown prose and masked examples, not executable Ruby or environment access. The skill still introduces real risks by installing an external package and offering an irreversible wipe operation.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (2)
🔑 Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/selan-ai-whatileaked/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/selan-ai-whatileaked?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/selan-ai-whatileaked?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/selan-ai-whatileaked/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/selan-ai-whatileaked.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
selan-ai. (2026). whatileaked security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/selan-ai-whatileaked/audits/1BibTeX citation
@techreport{selan-ai-selan-ai-whatileaked-2026,
author = {selan-ai},
title = {whatileaked security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/selan-ai-whatileaked/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "whatileaked security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "selan-ai"
date-released: "2026-08-30"
url: "https://skillstore.io/skills/selan-ai-whatileaked/audits/1"
identifiers:
- type: other
value: "skillstore:selan-ai-whatileaked:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Audit a developer workstation
Find credentials retained in local coding-agent histories before sharing or transferring a machine.
Investigate a credential exposure
Identify affected projects, files, and repeated appearances during incident response.
Prepare managed devices for reassignment
Review agent history findings and plan credential rotation before approved cleanup.
Try These Prompts
Check whether whatileaked is available, then scan my local supported agent histories. Do not install anything without asking.
Review the whatileaked results and explain which findings appear real, which may be fixtures, and which credentials need rotation.
Use the scan results to create a prioritized rotation and cleanup plan. Group repeated fingerprints as the same credential.
Review every file that the wipe operation would change. Proceed only after my explicit request and never answer its confirmation prompt automatically.
Best Practices
- Rotate confirmed credentials before deleting local copies.
- Review masked context and repeated fingerprints before classifying findings.
- Require explicit approval for installation and every destructive cleanup action.
Avoid
- Do not treat local deletion as credential revocation.
- Do not paste raw credentials into follow-up prompts or reports.
- Do not automate or bypass the wipe confirmation prompt.