xiaoyaoclaw-usage-report@1.0.9
VERIFIED· install onlyPublisher claims: "OpenClaw usage and performance reporting. Parse session JSONL to answer how long each agent task took, which tools/skills/models were used, and how many tokens were consumed — zero dependency, local only, no cost dimension (the script reads, computes and outputs no cost fields at all; token is the primary metric). Read-only: never modifies any file. Outputs are aggregated statistics only: no conversation content, no session identifiers (session-level detail is opt-in via --include-sessions) and no credential fields. The time window is a hard boundary: with a window selected (or the default "today") every dimension aggregates in-window events only, and full history requires the explicit --all flag. Documentation, report and JSON output follow the same scope; links in the docs are human-readable references, the runtime script makes no network calls. Report text defaults to Chinese and can be adapted to the user's language; the skill imposes no language or region restriction. Use when the user asks about token usage, task duration, slowest tools, skill usage, or per-agent consumption (今天花了多少 token/哪个工具最慢/ 任务耗时/用量报告), or scheduled via cron. 中文:OpenClaw 用量与性能查询。 解析 session JSONL,回答每次 agent 任务耗时、所用工具/技能/模型、token 消耗。零依赖纯本地,不提供成本维度(token 为主指标)。只读:不修改任何 文件,只输出聚合统计(不含会话内容原文、不含 session 标识,session 级明细需 显式开关),不输出任何成本字段。用户问 token 用量、任务耗时、最慢工具、 技能使用、按 agent 消耗时使用。cron 每日日报为可选项,须用户显式要求 并确认后自行设置。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 1.0.7
vet-skills diff xiaoyaoclaw-usage-report 1.0.7 1.0.9In the sandbox, this version reached for nothing 1.0.7 did not. Compared from the two recorded runs, not from source.
1.0.7 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-16 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
No findings across 1,503 lines in 10 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.