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 agentmods add commands/jackofall1232/l00prite/heartbeatgit clone --depth 1 https://github.com/jackofall1232/l00priteWrote 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/commands/jackofall1232/l00prite/heartbeat)<a href="https://agentmods.dev/commands/jackofall1232/l00prite/heartbeat"><img src="https://agentmods.dev/badge/commands/jackofall1232/l00prite/heartbeat.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.00000 | $0.00808 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
heartbeat 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heartbeat Prompt
Path convention: every
.l00prite/path in this prompt is relative to the protocol root — the directory that contains the.l00prite/folder. In a project scaffolded by build-loop that is thel00prite/directory at the repo root (memory atl00prite/.l00prite/); in the l00prite source repo it is the repo root itself.
You are performing a l00prite heartbeat check. Do not implement features during this check.
Read first
.l00prite/blueprint.md.l00prite/ledger.md.l00prite/todos.md.l00prite/state.json.l00prite/heartbeat.json.l00prite/lock.json.l00prite/events/pending/.l00prite/events/processing/
Checks
Determine:
- Is the project complete according to the blueprint and completion criteria?
- Is the current run blocked?
- Are there pending events?
- Are there failed CI events?
- Are there PR review events?
- Is human review required by a gate, event, or stop condition?
- Should the next loop process an event before normal roadmap work?
- Has
current_iterationreached or exceededmax_iterations? - Is
.l00prite/lock.jsoncurrentlyactiveand not expired, and if so, who owns it? - Is an execution run recorded as active (
state.json.execution_active: true), and if so, is it genuinely live (its lock still active and unexpired) or stale? A stale execution flag with no live lock means the run crashed — recommend recovery per.l00prite/prompts/execute-loop.mdrather than treating the project as running. - Should the next loop continue, pause, or stop?
Precedence rules
When signals disagree, resolve in this order:
- An active, non-expired lock held by a different agent or session wins over any recommendation to
continue — recommend
pauseuntil it is released or expires. state.json.blocked: truewins overheartbeat.json.should_continue.- Human review gates win over normal roadmap work.
- Failed CI / PR review / other blocker-priority events outrank normal roadmap tasks.
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 · 73 lines · 0 tokens per session scan A 0bc2571cdce4
heartbeat is a command published in the GitHub repository jackofall1232/l00prite (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 808 tokens. 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-31.
Other commands, from other repositories
annotate-plan
Draft a plan and open it in the annotator UI for user review.
docs
Command "docs" from tilework-tech/nori-skillsets, covering noridoc: commands, how it fits into the larger codebase, core implementation and things to know.
init
Scaffold a new plugin marketplace, or a standalone plugin.
bump
Version a local plugin from its commits and sync everything downstream.
build
Generate the Codex and Cursor registries from the catalog.
sync
Reconcile the catalog and the docs with the plugins on disk.