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/heartbeat-log)<a href="https://agentmods.dev/skills/wotai-dev/woterclip/heartbeat-log"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/heartbeat-log/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/wotai-dev/woterclip/heartbeat-log"><img src="https://agentmods.dev/badge/skills/wotai-dev/woterclip/heartbeat-log.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00888 |
| Opus 5 | $0.00030 | $0.00444 |
| Sonnet 5 | $0.00012 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
heartbeat-log 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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heartbeat Log
Parse and summarize the WoterClip heartbeat log file (.woterclip/heartbeat-log.jsonl).
Log Format
Each line is a JSON object in one of two kinds, distinguished by type. Full field
definitions live in ${CLAUDE_PLUGIN_ROOT}/references/beat-economics.md.
Issue line — one per issue worked. A line with no type key is an issue line, which is
what makes every pre-contract line readable without migration:
{"heartbeat": 7, "timestamp": "2026-03-25T10:15:00Z", "issue": "#79", "persona": "backend", "duration_sec": 720, "status": "in_progress", "actions": ["committed a1b2c3d", "created sub-issue #83"]}
Beat line — one per beat, carrying the beat's cost and why it stopped:
{"type": "beat", "started_at": "2026-03-25T10:03:00Z", "ended_at": "2026-03-25T10:17:05Z", "beat_elapsed_sec": 845, "issues_worked": 2, "stop_reason": "time_ceiling"}
Treat a missing field as unavailable, never as zero. Lines written before this contract
carry no duration_sec value and have no accompanying beat line. Render those as —; counting
them as 0 would report a beat that ran for minutes as free, and would drag any average toward
zero.
Procedure
Step 1: Read Log
Read .woterclip/heartbeat-log.jsonl. If missing or empty, report "No heartbeat history found."
Parse each line as JSON. Handle malformed lines gracefully (skip with warning).
Step 2: Summarize
Recent activity (default: last 10 issue lines — beat lines are excluded from this view; see the aggregate stats below for beat-level figures):
Heartbeat History
─────────────────
#7 10:15 backend #79 In Progress (12 min)
#6 09:45 backend #81 Completed (8 min)
#5 09:15 ceo #80 Triaged (4 min)
Aggregate stats (when asked for analytics or summary):
- Total issue lines, and total beats (count of beat lines)
- Heartbeats per persona (breakdown)
- Average duration per persona — over issue lines that carry
duration_seconly, stating how many lines were excluded as unavailable - Total and average
beat_elapsed_secacross beat lines - Stop-reason breakdown (how many beats hit
time_ceilingvsissue_budgetvscomplete) - Completion rate (completed / total)
- Most active issues (by heartbeat count)
- Blocked issues and duration blocked
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.
- 10d ago First seen · 76 lines · 60 tokens per session scan A 38d9ec5bcdbb
heartbeat-log is a skill published in the GitHub repository wotai-dev/woterclip (57 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 888 once invoked, about $0.0003 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.