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 email-setupgit 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/email-setup)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/email-setup"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/email-setup/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/email-setup"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/email-setup.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.00026 | $0.00909 |
| Opus 5 | $0.00013 | $0.00454 |
| Sonnet 5 | $0.00005 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
email-setup 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 9d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are setting up your own custom domain and email address. This is a one-time operation — once you have a domain and email, you do not need to run this again.
Prerequisites
Only proceed if the user explicitly asks you to create or set up your own (the assistant's) email address — e.g., "set up your email", "create your email address", "I want you to have your own email". Generic email requests like "send an email", "check my email", or "set up email" are about the user's personal email and should be handled by the Messaging skill, not this one. Do NOT proactively run this skill.
Step 1: Check if Domain & Email Already Exist
assistant domain status --json
assistant email status --json
If both commands show an active domain and email address, tell the user the existing address and stop.
If an email exists but no domain, the email was set up under the legacy shared domain — it still works. Ask the user if they want to keep it or migrate to a custom subdomain.
Step 2: Register Your Domain
Each assistant gets its own subdomain (e.g. mybot.vellum.me). This must be registered before creating an email address.
assistant domain register <subdomain>
For <subdomain>, use your assistant name (lowercased, alphanumeric, hyphens allowed). Check your identity from IDENTITY.md to determine your name. If you don't have a name yet, ask the user what subdomain they'd like.
If the domain is already registered, domain status will show it — skip to Step 3.
Step 3: Register Your Email
Once the domain is active, register your email username on that domain:
assistant email register <username>
This creates <username>@<subdomain>.vellum.me. Use the same name as your subdomain for simplicity (e.g. [email protected]), or ask the user if they prefer a different local part.
Step 4: Verify Status
assistant email status --json
Confirm the address is active.
Step 5: Confirm Setup
- Tell the user your new email address.
- Store a note in your memory that your domain and email have been provisioned.
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.
- 9d ago First seen · 96 lines · 26 tokens per session scan A 4e8376250f9b
email-setup is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,214 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 909 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-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.