تخطَّ إلى المحتوى
TakoAPI
العودة إلى المهارات

leak-check

بواسطة khaney64

Coding Agents & IDEs
563التنزيلات وفق ما يذكره clawskills.sh
0المشاهدات
لا إعجاباتسجّل الدخول للإعجاب بهذه المهارة
—لم يُقيَّم بعد
تقييمك

موجز

Scan session logs for leaked credentials.

الوصف

ما الذي تفعله هذه المهارة

Scans OpenClaw session JSONL files for credentials that may have been sent to AI providers. Matches credential fragments against configurable patterns and identifies which provider (Anthropic, OpenAI, Google, etc.) received the data. Distinguishes real leaks from config echoes where the config file itself was read during a session.

Runs entirely local with no network access, no dependencies, and no file writes, so it can be trusted to scan sensitive session data without risk of further exposure.

متى تستخدمها

  • Checking if an API key was accidentally sent to an AI model
  • Auditing past sessions after a suspected credential exposure
  • Verifying no secrets leaked before sharing session logs
  • Running a post-incident scan across all stored sessions
  • Monitoring which AI providers received sensitive data

مثال على سير العمل

الإدخال

User asks: check if any of my credentials leaked in recent sessions

الوكيل
  1. 1

    Read leak-check.json config from ~/.openclaw/credentials/ to load credential fragments

  2. 2

    Scan all JSONL files in ~/.openclaw/agents/main/sessions/

  3. 3

    Match each session's content against configured wildcard patterns

  4. 4

    Distinguish config echoes (where config file was read) from real leaks

  5. 5

    Report matched credentials with session ID, timestamp, and provider name

الإخراج

Discord-formatted report listing 2 leaked credentials with session IDs and providers, or a clean confirmation if none found

المتطلبات

  • leak-check.json config file with credential fragments to search for

التثبيت

clawhub install khaney64/leak-check

شغّل أمر واجهة سطر الأوامر، أو الصق النص في Claude Code أو Cursor أو Codex أو أي وكيل برمجة تستخدمه.

الروابط