Token Optimizer 1.0.0

✂️ TOKEN节约器 - 工作流程控制器。通过问题预检、路径验证、进度检查、错误快速定位，防止重复无效工作，节约TOKEN消耗。兼容Windows/Mac/Linux/MaxClaw/ClawHub。

This skill appears to be a local diagnostic/workflow helper and includes code/instructions that run system commands (netstat/lsof/pgrep/powershell), check files, and inspect processes and environment variables. That's plausible for a 'pre-check' tool, but it also means the skill — if executed — can read sensitive local state (open ports, running processes, files, env vars). The SKILL.md sample constructs shell commands by interpolating user-supplied values, which can lead to command injection if inputs aren't strictly validated. Before installing or enabling this skill: - Treat it as powerful: only enable it for trusted agents in a controlled environment (or sandbox). - Ask the publisher for provenance (source code repository, homepage, who is 'Matrix Agent') since 'Source' is unknown. - Request explicit documentation on what exact paths/commands the skill will run and what inputs it will accept; prefer whitelists and input sanitization. - If you must use it, avoid granting it access to sensitive directories or credentials; test it in a disposable environment first. Confidence is medium because the behavior is coherent with a diagnostics tool, but the instruction-level use of shell commands and lack of provenance/constraint make the package risky without further clarification.

Type: OpenClaw Skill Name: token-optimizer-1-0-0 Version: 1.2.0 The skill bundle provides a workflow management tool designed to optimize token usage through environment pre-checks and error localization. However, the JavaScript code provided in `SKILL.md` (specifically the `PreChecker` class) contains critical shell injection vulnerabilities. It uses `child_process.execSync` to execute system commands like `netstat`, `lsof`, and `pgrep` while directly interpolating variables (`port`, `processName`) into the command strings without any sanitization. While these capabilities are consistent with the stated purpose of diagnostic checking, the insecure implementation poses a significant RCE risk if the agent processes untrusted input through these functions.