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.์์ด์ ํธ๋ ๊ณ์ํด์ ๊ณํ์ ํ์ํ๊ณ ๋ณด์ ์ ์ฑ ์์ ์๊ตฌํ๋ ํ์ธ์ ์์ฒญํด์ผ ํฉ๋๋ค.
์์ด์ ํธ๊ฐ ์ฝ๊ธฐ ์ฌ์ด ๋ฆฌ์์ค
AI ์์ด์ ํธ, ํฌ๋กค๋ฌ, ์คํฌ๋ฆฝํธ๊ฐ ์ ์ฒด ํ์ด์ง ๋์ ์ ๋ฆฌ๋ ์ปจํ ์คํธ๋ง ํ์ํ ๋ ์ด ๋งํฌ๋ฅผ ์ฌ์ฉํ์ธ์.
ํ ์คํธํด ๋ณด๊ธฐ
"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.
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
Does the scan change my files?
Does the output reveal my credentials?
What does a matching fingerprint mean?
Can deleting local history recover a leaked credential?
Why might a finding be harmless?
Is the wipe operation reversible?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
selan-ai๋ผ์ด์ ์ค
MIT
Skillstore ๋ฆฌ๋น์
r1
๋ฒ์ ์๋ด
์์ฑ์๊ฐ ๋ฒ์ ์ ์ ์ธํ์ง ์์์ต๋๋ค.
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/selan-ai/whatileaked/tree/d264249417f1db8624f54d11ea66852ae2f825e6/skills/whatileaked์ฐธ์กฐ
f5d1008064a1cff356fa4ef081843059e09c5d5a
์ ์ง๋ณด์ ์ต์ ์ฑ
2026. 8. 30.
์ฌ์ฉ๋
1 ๋ค์ด๋ก๋ ยท 1 ์กฐํ
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md