leak-check

Scan OpenClaw session JSONL files for leaked credential patterns and identify external AI providers.

7|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/SJTU-IPADS/SkVM-data --skill leak-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: leak-check
Source: https://github.com/SJTU-IPADS/SkVM-data/tree/main/skills/leak-check
Command: npx skills add https://github.com/SJTU-IPADS/SkVM-data --skill leak-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Credentials can be leaked in OpenClaw session logs, exposing tokens and keys. This skill scans JSONL session files to identify where credentials appeared and flags which external AI provider received the data.

Core Features & Use Cases

  • Scan OpenClaw session JSONL files for leaked credentials by matching patterns against known credential formats.
  • Distinguish real leaks from internal echoes by detecting when credential definitions appear in logs.
  • Provide per-session, per-credential details including session ID, timestamp, and provider information.

Quick Start

Run the leak-check script to scan your OpenClaw session logs for leaked credentials.

Frequently Asked Questions about leak-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect leaked credentials in OpenClaw session logs?

Scanning JSONL session files with the leak-check script detects leaked credentials by matching content against configured credential patterns. It distinguishes actual external provider data exposure from harmless internal delivery echoes.

How does credential leak detection distinguish real leaks from internal echoes?

Credential leak detection distinguishes real leaks from internal echoes by identifying when credential definitions appear within the JSONL session logs. It ignores these harmless internal echoes and flags actual data exposure to external AI providers.

Can I track which external AI provider received leaked credentials in JSONL files?

Yes, you can track which external AI provider received leaked credentials in JSONL files. The scan resolves provider information across all stored session files, providing per-session and per-credential details including session ID and timestamp.

What details are provided for each leaked credential found in session logs?

The scan provides per-session and per-credential details for each leaked credential found in session logs. This includes the specific session ID, timestamp, and the external AI provider information associated with the data exposure.

Are the results of scanning JSONL session files for credential leaks deterministic?

Yes, the results of scanning JSONL session files for credential leaks are deterministic. The leak-check script ensures consistent outcomes by applying configured patterns, session tracking, and provider resolution logic across all scans.