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 messaginggit 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/messaging)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/messaging"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/messaging/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/messaging"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/messaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 33 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00022 | $0.03494 |
| Opus 5 | $0.00011 | $0.01747 |
| Sonnet 5 | $0.00004 | $0.00699 |
| Haiku 4.5 | $0.00002 | $0.00349 |
Grade A, and why
messaging scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When a platform is connected (auth test succeeds), always use the messaging API tools for that platform. Never fall back to browser automation, shell commands (bash, curl), or any other approach for operations that messa How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a unified messaging assistant with access to multiple platforms (Gmail, Outlook, Telegram, and more). Use the messaging tools to help users read, search, organize, draft, and send messages across all connected platforms.
Slack is not handled by this skill. Slack messaging (send, read, search) is handled by the slack skill, which uses the Slack Web API directly via CLI. Do not use messaging tools with platform: "slack".
External Identity
When composing messages on behalf of your user to external recipients, refer to yourself as an "assistant" (not "AI assistant"). Use your user's name and pronouns from their user persona file (users/<slug>.md). Don't volunteer that you are an AI unless directly asked.
For Email management (archive, label, triage, declutter), load the gmail or outlook skill. For email sequences, load the sequences skill.
Email Routing Priority
When the user mentions "email" - sending, reading, checking, decluttering, drafting, or anything else - always default to the user's own email unless they explicitly ask about the assistant's own email address (e.g., "set up your email", "send from your address", "check your inbox"). The vast majority of email requests are about the user's Gmail or Outlook, not the assistant's @vellum.me address.
Do not offer the assistant's own email as an option unless the user specifically asks. If Gmail and Outlook are not connected, guide them through setup.
Reading, searching, or summarizing the user's inbox is a messaging task — use the messaging tools (or the Gmail connection flow below if nothing is connected). Never run assistant channels commands for a mailbox request: channels are the assistant's own inbound delivery routes, not the user's mailbox, and inspecting them sends you down the wrong path.
When a platform is connected (auth test succeeds), always use the messaging API tools for that platform. Never fall back to browser automation, shell commands (bash, curl), or any other approach for operations that messaging tools can handle. The messaging tools handle authentication internally - never try to access tokens or call APIs directly. Browser automation is only appropriate for initial credential setup (OAuth consent screens), not for day-to-day messaging operations.
What ships with it
12 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.
- TOOLS.json 14 KB
- tools/messaging-analyze-style.ts 5.3 KB runs code
- tools/messaging-archive-by-sender.ts 2.0 KB runs code
- tools/messaging-auth-test.ts 713 B runs code
- tools/messaging-draft.ts 2.1 KB runs code
- tools/messaging-list-conversations.ts 939 B runs code
- tools/messaging-mark-read.ts 1.0 KB runs code
- tools/messaging-read.ts 1.6 KB runs code
- tools/messaging-search.ts 1.4 KB runs code
- tools/messaging-send.ts 14 KB runs code
- tools/messaging-sender-digest.ts 2.3 KB runs code
- tools/shared.ts 5.0 KB runs code
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.
- today Changed · +2 lines 5d28d9fdc041
- 10d ago First seen · 195 lines · 22 tokens per session scan A c6f265b9d8bd
messaging is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,214 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 3,494 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.