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.
安装前请停下并请求确认。
请审查安装计划，并在更改文件前获得用户明确同意。
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
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.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“whatileaked”。 Scan my coding-agent histories for leaked credentials.
预期结果:
The scan found two fingerprints across three files. Rotate the likely production credential before considering local cleanup.
正在使用“whatileaked”。 Are these two findings the same credential?
预期结果:
Yes. The matching fingerprint indicates one credential appeared in both locations, although the secret itself remains masked.
正在使用“whatileaked”。 Help me interpret a masked test-key finding.
预期结果:
- 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.
安全审计
高风险All 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.
已确认安全问题 (2)
风险因素
⚙️ 外部命令 (2)
🔑 环境变量 (1)
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/selan-ai-whatileaked/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/selan-ai-whatileaked?utm_source=security_passport_badge)HTML 徽章
<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>嵌入卡片
<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>学术引用 (APA · BibTeX · CFF)
APA 引用
selan-ai. (2026). whatileaked security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/selan-ai-whatileaked/audits/1BibTeX 引用
@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 评分
评分依据 证据置信度: 中你能构建什么
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.
试试这些提示
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.
最佳实践
- 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.
避免
- 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.