Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Analyze OpenClaw costs and detect billing issues. Source code is fully bundled — nothing is fetched at runtime. Requires only the node binary.
Analyze OpenClaw costs and detect billing issues. Source code is fully bundled — nothing is fetched at runtime. Requires only the node binary.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Cost forensics for OpenClaw. Finds billing issues in your config, sessions, and workspace. Pure deterministic logic — no AI, no network calls, no external dependencies. Source code is fully bundled in this skill folder. Nothing is fetched at runtime. You can audit every file before running. Files this skill reads: ~/.openclaw/openclaw.json — your OpenClaw config ~/.openclaw/agents/main/sessions/sessions.json — session token usage ~/clawd/ — workspace root file count only (no file contents read) /tmp/openclaw — log directory (read only, if present) Files this skill may write (only when --md is used): ./clawculator-report.md — markdown report Custom path via --out=PATH No network requests are made. No shell commands are spawned. Session keys are truncated in all output (first 8 chars + ellipsis) to avoid exposing sensitive identifiers. Usage When the user types clawculator, check my costs, analyze spend, or cost report, run: node {baseDir}/run.js --md Return the full markdown report to the user inline. When the user types snapshot, share my grade, cost grade, clawculator snapshot, or what's my grade, run: node {baseDir}/run.js --snapshot Return the terminal card output to the user. This shows their grade (A+ to D), cost range, setup complexity, and findings — designed to be screenshot and shared. Flags --snapshot — shareable grade card (terminal output, screenshot-ready) --md — write markdown report and print to stdout --json — machine-readable JSON to stdout --out=PATH — custom output path for --md node {baseDir}/run.js --help — full usage What it catches 💓 Heartbeat running on paid model instead of Ollama 🔧 Skill polling loops on paid model 📱 WhatsApp groups auto-joined on primary model 🪝 Hooks (boot-md, command-logger, session-memory) on Sonnet 💬 Orphaned sessions still holding tokens 🤖 maxConcurrent too high — burst cost multiplier 📁 Workspace root bloat inflating context ⚙️ Primary model cost awareness All findings include exact fix commands.
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.