Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add wotai-dev/woterclip/plugin install woterclipWrote 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/wotai-dev/woterclip/status)<a href="https://agentmods.dev/skills/wotai-dev/woterclip/status"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/status.svg" alt="Measured on agentmods" height="20"></a>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.00071 | $0.01584 |
| Opus 5 | $0.00036 | $0.00792 |
| Sonnet 5 | $0.00014 | $0.00317 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
woterclip-status scanned grade A with 0 findings 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 6d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WoterClip Status
Display the current state of WoterClip in this repository: schedule info, last heartbeat, issue activity, queue, and blocked items.
Arguments:
--history— Show recent heartbeat history from the log file
Status Procedure
Step 1: Load Config
Read .woterclip/config.yaml. If missing, report that WoterClip is not initialized and suggest /woterclip-init.
Step 2: Check Schedule
Determine schedule state at read time by asking the harness what recurring work it has registered for this repo (its schedule/cron listing, or the equivalent surface for the loop primitive in use).
Report one of three states, and never infer one from another:
- Scheduled — a recurring heartbeat is registered. Report its cadence.
- Not scheduled — the harness returned a listing and no heartbeat is in it.
- Unknown — the harness exposes no way to enumerate schedules, or the query failed.
Report Unknown rather than Not scheduled whenever the listing is unavailable. A false "not scheduled" tells the Board their automation is off when it may be running.
Step 3: Last Beat
Read the tail of .woterclip/heartbeat-log.jsonl (e.g. tail -n 50) and scan backwards for the most recent beat line and the most recent issue line — the log is append-only and never rotated, so do not read the whole file for this view. Line kinds, grouping, and fields are defined in ${CLAUDE_PLUGIN_ROOT}/references/beat-economics.md.
From the last beat line, report:
- When the beat ran and how long ago
beat_elapsed_secas the beat's cost, andissues_workedstop_reason— surfacetime_ceilingandissue_budgetprominently, since both mean work was left on the queue
From the last issue line, report:
- Heartbeat number, persona, and issue
- Outcome (completed, in progress, blocked, triaged, decomposed)
The Stopped determination needs the queue, so it is made at the end of step 4 — see there.
Absent fields render as —, never as 0. A line with no type key is an issue line — old and new alike, since only beat lines carry type. A beat with no beat line has an unavailable cost, not a zero one. Do not sum issue-line durations to synthesize a missing beat cost — issue durations exclude the loop's own overhead.
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.
- 6d ago First seen · 118 lines · 71 tokens per session scan A 0463d4d3a6a8
woterclip-status is a skill published in the GitHub repository wotai-dev/woterclip (57 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,584 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
houseclean
Cross-drive storage audit and cleanup. Surveys all drives, finds orphaned git worktrees, large AI tool caches (.ollama, .gemini, .cursor, npm, pip), and buildable artifacts (nodemodules, .venv). Produces a prioritized action plan with specific migration commands. Use when disk space is low or worktrees need cleanup…
garbage-collection
This skill should be used when the user asks about "garbage collection rules", "entropy fighting", "documentation staleness", "dead code detection", "convention drift", "periodic checks", "auto-fix rules", or needs guidance on the Garbage Collection section of HARNESS.md.
quick-wrap
Short session close: commit, handle loose ends, stop. Not workstream-complete.
workstream-start
Orient session — preflight, load context, choose work.
handoff
Mid-workstream save-state under context pressure — always a continuation.
setup
Install-chain walker (step 5/5) — verifies claude-klabauter, finishes install.