Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Data Analysis
Leak Check
Scan session logs for leaked credentials. Checks JSONL session files against known credential patterns and reports which AI provider received the data.
skill openclawclawhub Free
Scan session logs for leaked credentials. Checks JSONL session files against known credential patterns and reports which AI provider received the data.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, scripts/leak-check.js
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.7
Provenance
- Publisher
- khaney64
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Leak Check
Scan OpenClaw session JSONL files for leaked credentials. Reports which real AI provider (anthropic, openai, google, etc.) received the data, skipping internal delivery echoes.
Quick Start
# Check for leaked credentials (default: discord format) node scripts/leak-check.js # JSON output node scripts/leak-check.js --format json
Configuration
Credentials to check are defined in leak-check.json. The script searches for this file in order: Skill directory (./leak-check.json) — for backward compatibility ~/.openclaw/credentials/leak-check.json — recommended persistent location (survives skill updates via clawhub) Since clawhub clears the skill directory on updates, place your config in ~/.openclaw/credentials/ to avoid losing it: mkdir -p ~/.openclaw/credentials cp leak-check.json ~/.openclaw/credentials/leak-check.json You can also specify an explicit path with --config. [ { "name": "Discord", "search": "abc*xyz" }, { "name": "Postmark", "search": "k7Qm9x" } ] Important: Do not store full credentials in this file. Use only a partial fragment — enough to uniquely identify the credential via a contains, begins-with, or ends-with match. Wildcard patterns: abc* — starts with "abc" *xyz — ends with "xyz" abc*xyz — starts with "abc" AND ends with "xyz" abc (no asterisk) — contains "abc" "" (empty) — skip this credential
Options
--format <type> — Output format: discord (default) or json --config <path> — Path to credential config file (default: ./leak-check.json, then ~/.openclaw/credentials/leak-check.json) --help, -h — Show help message
Discord (Default)
🔐 **Credential Leak Check** ⚠️ **2 leaked credentials found** **Discord Token** • Session: `abc12345` | 2026-02-14 18:30 UTC | Provider: anthropic **Postmark** • Session: `def67890` | 2026-02-10 09:15 UTC | Provider: anthropic Or if clean: 🔐 **Credential Leak Check** ✅ No leaked credentials found (checked 370 files, 7 credentials)
Config Echoes
If the leak-check.json config file is read or discussed during an OpenClaw session, the credential patterns will appear in that session's JSONL log. The scanner detects this and reports these matches separately as config echoes rather than real leaks: 📋 **3 possible config echoes** (session contains leak-check config) • **Discord**: 1 session ... ✅ No credential leaks beyond config echoes Config echoes will continue to appear on every run until the session file is removed. To clear them, delete the session file from ~/.openclaw/agents/main/sessions/: rm ~/.openclaw/agents/main/sessions/<session-uuid>.jsonl Tip: Avoid reading or referencing leak-check.json during an OpenClaw session. If it happens, note the session ID from the report and delete it.
JSON
{ "leaks": [ { "credential": "Discord Token", "session": "abc12345", "timestamp": "2026-02-14T18:30:00.000Z", "provider": "anthropic" } ], "configEchoes": [ { "credential": "Gateway", "session": "b175e53c", "timestamp": "2026-02-19T18:00:30.067Z", "provider": "minimax-portal", "configEcho": true } ], "summary": { "filesScanned": 370, "credentialsChecked": 7, "leaksFound": 2, "configEchoesFound": 1 } }
Security
This skill is designed to be local-only and read-only. The following properties can be verified by inspecting scripts/leak-check.js: No network access — no use of http, https, net, dgram, fetch, WebSocket, or any network API No child processes — no use of child_process, exec, spawn, or execSync No external dependencies — zero npm packages; only Node.js built-ins (fs, path, os) No dynamic code execution — no eval(), Function(), or dynamic require()/import() No file writes — only fs.readFileSync, fs.existsSync, and fs.readdirSync are used; no files are created, modified, or deleted No environment variable access — does not read process.env Output is stdout only — all results go to console.log; nothing is sent elsewhere
Verify It Yourself
Confirm no unexpected APIs are used anywhere in the script: grep -E 'require\(|import |http|fetch|net\.|dgram|child_process|exec|spawn|eval\(|Function\(|\.write|\.unlink|\.rename|process\.env' scripts/leak-check.js Expected output — only the three built-in require() calls at the top of the file: const fs = require('fs'); const path = require('path'); const os = require('os');
Category context
Data access, storage, extraction, analysis, reporting, and insight generation.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Scripts
- SKILL.md
- scripts/leak-check.js