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.
توقف واطلب التأكيد قبل التثبيت.
راجع الخطة واحصل على موافقة صريحة من المستخدم قبل تغيير الملفات.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف 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.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "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 الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/selan-ai-whatileaked/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](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/1اقتباس BibTeX
@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.