Stop Burning Tokens — OpenClaw Cost Diagnostic Primer
v1.0.0Diagnostic framework to identify and reduce token waste in OpenClaw deployments, cutting costs by applying efficient data handling and model use practices.
⭐ 0· 41·0 current·0 all-time
by~K¹yle Million@thebrierfox
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (token-cost diagnostics) match the SKILL.md content. The skill is purely advisory and requests no env vars, binaries, or install steps that would be unrelated to cost optimization.
Instruction Scope
SKILL.md contains diagnostic questions, cost comparisons, and operational recommendations (indexing, caching, model routing). It does not instruct the agent to read arbitrary files, exfiltrate data, or access environment variables or system paths beyond its advisory scope.
Install Mechanism
No install spec and no code files. Being instruction-only means nothing is written to disk or executed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. Recommendations (e.g., cache stable context) are conceptual and do not require extra secrets.
Persistence & Privilege
Flags show always:false and normal invocation behavior. The skill does not request persistent presence or modify other skills or system configuration.
Assessment
This skill is advisory only and appears safe to read/use: it gives best-practice diagnostics for reducing token costs and does not request credentials or install code. Before applying recommendations, (1) verify any external links or commercial offerings independently (the SKILL.md links to a ShopClawMart listing), (2) test changes (model routing, session caps, caching) in a staging environment to confirm actual savings, (3) be mindful of privacy/retention when caching or indexing context — avoid storing sensitive PII unless your storage and retention policies are reviewed, and (4) instrument and measure token usage before/after changes so you can validate claimed cost deltas. If you plan to operationalize the recommendations (implement caching, connector audits, or automated routing), review those implementation details for data-handling and credential use — the primer itself does not perform those actions.Like a lobster shell, security has layers — review code before you run it.
latestvk979kzbr5g569ytndmpvqhc50s8445x6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.