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 7df-lab/devo --skill rlm-heartbeatgit clone --depth 1 https://github.com/7df-lab/devoWrote 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/7df-lab/devo/rlm-heartbeat)<a href="https://agentmods.dev/skills/7df-lab/devo/rlm-heartbeat"><img src="https://agentmods.dev/badge/skills/7df-lab/devo/rlm-heartbeat/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/7df-lab/devo/rlm-heartbeat"><img src="https://agentmods.dev/badge/skills/7df-lab/devo/rlm-heartbeat.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.00046 | $0.00539 |
| Opus 5.5 | $0.00018 | $0.00216 |
| Sonnet 5.5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
rlm-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rlm-heartbeat — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RLM Heartbeat
RLM heartbeats are internal recurring prompts for the current agent session.
They are separate from the user's visible /heartbeat: this skill cannot read,
replace, pause, resume, or clear that user-level heartbeat.
Call directly from the Python REPL:
await rlm_heartbeat.create("check test progress", interval="5m", label="tests")
await rlm_heartbeat.create("watch build", delivery_mode="follow_up")
await rlm_heartbeat.list()
await rlm_heartbeat.update("job-id", status="pause")
await rlm_heartbeat.delete("job-id")
API
await rlm_heartbeat.list(include_inactive=False)— list this session's internal RLM heartbeats. By default this includes active and paused entries.await rlm_heartbeat.create(instruction, interval=None, label=None, delivery_mode=None)— create a recurring heartbeat for this session. The default interval is every 5 minutes. Multiple RLM heartbeats may run at once; use labels to distinguish them.delivery_modeis"steer"(default) or"follow_up".await rlm_heartbeat.update(id, instruction=None, interval=None, label=None, status=None, delivery_mode=None)— update one RLM heartbeat by id.statusmay be"pause"or"resume";delivery_modemay be"steer"or"follow_up".await rlm_heartbeat.delete(id)— cancel one RLM heartbeat by id.
Delivery mode
Each heartbeat has a delivery mode controlling how the scheduled prompt reaches the session when it is busy:
steer(default): interrupt the current turn so the heartbeat runs promptly.follow_up: wait for the current turn to finish before running the heartbeat.
Rules
- Use this when the user asks you to start, create, schedule, or manage your own
heartbeat without explicitly referring to
/heartbeat. - Use this only for agent-internal recurring checks and long-running task coordination.
- Do not use this skill to satisfy a user's request to configure
/heartbeat; that is a separate user-level surface. - Keep heartbeat instructions specific and actionable so each recurring turn knows exactly what to inspect or continue.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 55 lines · 46 tokens per session scan A 021daa60f9e9
rlm-heartbeat is a skill published in the GitHub repository 7df-lab/devo (321 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 539 once invoked, about $0.0002 per session on Opus 5.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-10-06.
Other skills, from other repositories
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
plugin-creator
Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…
codex-pr-body
Update the title and body of one or more pull requests.
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
remote-tests
Testing against remote executors in integration tests.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.