Vellum Assistant is a personal AI assistant that remembers information about users, learns their preferences, and takes actions across connected apps. It is intended for people who want an assistant that can manage conversations, unfinished work, and proactive notifications over time. The catalogue skills, hooks, instruction, and setting configure or extend how the assistant works.
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 vellum-ai/vellum-assistant --skill vellum-heartbeatgit clone --depth 1 https://github.com/vellum-ai/vellum-assistantWrote 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/vellum-ai/vellum-assistant/vellum-heartbeat)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/vellum-heartbeat"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/vellum-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/vellum-ai/vellum-assistant/vellum-heartbeat"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/vellum-heartbeat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.00469 |
| Opus 5 | $0.00005 | $0.00234 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
vellum-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 3d 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.
What it actually says
The heartbeat feature runs your HEARTBEAT.md checklist periodically in a background conversation. Each run, the assistant works through the checklist and flags anything that needs attention.
Setup
Edit config.json using file_edit:
- Enable heartbeat: Set
heartbeat.enabledtotrue. - Set interval: Set
heartbeat.intervalMs(milliseconds between runs, default: 3600000 = 1 hour). - Optional active hours: Set
heartbeat.activeHoursStartandheartbeat.activeHoursEnd(0-23) to restrict runs to certain hours in the heartbeat timezone. Hours useheartbeat.timezonewhen set, otherwise the user's configured or detected timezone (the host clock is last resort). Both must be set together.
Example config.json heartbeat section:
{
"heartbeat": {
"enabled": true,
"intervalMs": 1800000,
"activeHoursStart": 8,
"activeHoursEnd": 22
}
}
Then edit HEARTBEAT.md with the checklist items. The assistant will work through this file each heartbeat run.
Notes
- Toggling
heartbeat.enabledrequires an assistant restart to take effect. - Changes to
HEARTBEAT.mdtake effect on the next heartbeat run (no restart needed). - The heartbeat runs in a separate background conversation, not the user's active chat.
Inference
Heartbeat runs use the heartbeatAgent call site, which by default resolves to the
cost-optimized profile so background checks stay cheap. Override via
llm.callSites.heartbeatAgent in workspace config (profile, provider, model,
effort, thinking — whatever the profile supports).
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.
- 3d ago Changed e55e277a44a1
- 9d ago First seen · 53 lines · 10 tokens per session scan A 7b34cf74cd1e
vellum-heartbeat is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,234 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 469 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
meeting-notes
Use when the user asks to capture, structure, or summarize meeting notes / call notes / 1:1 discussion / standup notes. Produces a standard template with attendees, agenda, decisions, action items (owner + deadline), and open questions.
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
ha-settings
Manage Hope Agent application settings through conversation. Use when the user wants to view or change any app configuration: theme, language, enhanced focus indicators, proxy, temperature, notifications, tool timeout, context compaction, automatic session titles, web search, GitHub issue reporting, memory, embedding…
relay
Write a handoff/continuity note for the NEXT Sutando session. Captures what was just in flight, what to check first, what might go wrong, and implicit context the structured snapshot doesn't carry. Drained into session-state.md by src/session-handoff.sh.
meeting-scheduler
Schedule a small meeting end-to-end: resolve attendee emails, check the owner's calendar for the slot, dedup-check, then create + email the Google Calendar invite. The mechanical core only — cross-person availability negotiation stays interactive.
x-twitter
Post to X via a signed-in browser session (live method — no API keys); API v2 path for search/read/engagement.