Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add KCNyu/clawock --skill openclaw-tunegit clone --depth 1 https://github.com/KCNyu/clawockWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kcnyu/clawock/openclaw-tune)<a href="https://agentmods.dev/skills/kcnyu/clawock/openclaw-tune"><img src="https://agentmods.dev/badge/skills/kcnyu/clawock/openclaw-tune/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kcnyu/clawock/openclaw-tune"><img src="https://agentmods.dev/badge/skills/kcnyu/clawock/openclaw-tune.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 44 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00140 | $0.02834 |
| Opus 5 | $0.00070 | $0.01417 |
| Sonnet 5 | $0.00028 | $0.00567 |
| Haiku 4.5 | $0.00014 | $0.00283 |
Grade A, and why
openclaw-tune scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf http://127.0.0.1:18789/health && echo " ✓ gateway up" How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Tune-Up
Use this skill to keep kcn's openclaw setup lean. Run it after every openclaw update, or as a periodic chore every 1-2 weeks.
When to invoke
- User says
/openclaw-tuneor优化下 openclaw - After
openclaw update(defaults may have shifted; configs may need migration) - When response feels slow / token costs creeping up
- When
agents/main/sessions/looks suspiciously large
Operating principles
- Don't delete, archive first: move stale files to
/tmp/openclaw-cleanup-<date>/so they can be recovered for a day - Verify before touching live state: if openclaw gateway is running, only touch files it doesn't actively hold (use
lsof) - Real holdings, real data: never propose changes that hardcode portfolio numbers —
portfolio.jsonis the only source of truth - Report what was done with sizes/counts; never silent fixes
Checklist
1. Disk bloat
Big offenders found historically:
| Path | What to look for | Action |
|---|---|---|
~/.openclaw/agents/main/sessions/*.bak-* |
Transcript backups, no rotation. One active session can accumulate 100+ files (7MB each = 700MB) | Keep latest 3 per session, archive rest |
~/.openclaw/agents/main/sessions/*.bak-* (orphan) |
.bak file with no matching .jsonl (session deleted but backup stayed) |
Archive all |
~/.openclaw/openclaw.json.clobbered.* |
Config corruption snapshots (e.g. 2026-04-25 had 78) | Archive all (the .last-good retains canonical state) |
~/.openclaw/logs/stability/*.json |
Crash dumps from past unhandled rejections | Archive if older than 30 days |
~/.openclaw/memory/main.sqlite.tmp-* |
Orphaned SQLite migration tmp file from interrupted write. Verify lsof returns empty, mtime > 7d, then delete |
Delete only if not held |
~/.openclaw/media/ |
Generated images, voice clips | Check size; archive if > 100MB and not referenced |
~/.openclaw/agents/main/sessions/*.trajectory.jsonl |
Audit trajectory logs — large but useful for debugging | Leave unless > 500MB total |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 220 lines · 140 tokens per session scan A 963e9d053f6a
openclaw-tune is a skill published in the GitHub repository KCNyu/clawock (14 stars, last pushed yesterday), licensed MIT. It adds 140 tokens to every session and 2,834 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
arxiv-agentic-verifier
Source Paper: Scaling Agentic Verifier for Competitive Coding (ID: 4a4c4dae6a5145ebc4d62eb2d64b0f0f) Type: Code Verification / Test Generation.
backtest-diagnose
Diagnose failed or underperforming backtests, locate the root cause, and fix the issue.
Logging
Where logs live and when to write them — errors, daily, system.
incident-response
Framework for managing incidents from detection through postmortem. Use during active incidents, for creating runbooks, or when conducting postmortems.
node-notready-triage
Use when nodes are NotReady or the whole cluster looks unhealthy — inspects node conditions, CNI/kube-system pods, and capacity to find what is keeping the kubelet or network from being ready.
pod-crashloop-triage
Use when pods are in CrashLoopBackOff, ImagePullBackOff, ErrImagePull, or OOMKilled — collects describe/logs/events and identifies the failure class before recommending a fix.