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.
Borrowing it
Nothing to install: this file belongs to vellum-ai/vellum-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vellum-ai/vellum-assistant/main/.cursor/skills/vellum-user-facing-copy/SKILL.mdgit 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-user-facing-copy)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/vellum-user-facing-copy"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/vellum-user-facing-copy/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-user-facing-copy"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/vellum-user-facing-copy.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.00063 | $0.00409 |
| Opus 5 | $0.00032 | $0.00204 |
| Sonnet 5 | $0.00013 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
vellum-user-facing-copy 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 12d 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
Vellum User-Facing Copy
Terminology
Use "assistant" in user-facing text. "Daemon" is an internal implementation detail and should only appear in internal code, internal comments, file paths, or architecture explanations intended for maintainers.
When unsure, ask: would a user ever read this? If yes, say "assistant".
Generic Examples
Never include real personal data in examples, fixtures, tests, docs, or commit messages.
Use:
- Names:
Alice,Bob,Example User - Emails:
[email protected],[email protected] - Phone numbers:
555-0100through555-0199 - IDs:
user-123,org-abc,conv-xyz
Avoid real names, personal emails, real phone numbers, account IDs, tokens, or private workspace paths.
Release Notes
There is currently no release-note surfacing mechanism — the workspace-bulletin feature was removed. Do not add new release-note workspace migrations; the historical set is frozen.
Error Messages
Good user-facing errors:
- explain what failed
- avoid exposing internals or secrets
- say what the user can do next when there is a clear action
- use consistent product terminology
Avoid stack traces, implementation-only vocabulary, and ambiguous "something went wrong" messages when a concrete cause is available.
Review Workflow
- Identify text users may read.
- Check terminology, privacy, and clarity.
- Check whether the copy implies unavailable or flagged behavior.
- Preserve technical precision while removing internal jargon.
- Recommend tests or snapshots when copy is part of a stable interface.
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.
- 12d ago First seen · 49 lines · 63 tokens per session scan A ba48bc507f00
vellum-user-facing-copy is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,234 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 409 once invoked, about $0.0003 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
lictor-security-check
Pre-release security audit for ANY project — AI-built or hand-written, web or mobile. Scans the codebase for the full range of real-world risks that get apps breached: leaked API & AI-provider keys, exposed configs/secrets, broken auth & access control (IDOR), injection (SQL/XSS/command), SSRF, open databases & cloud…
lictor-rotate
Walks the user through rotating a leaked API key — step by step, provider-specific. Knows the exact URL to visit, the exact button to click, and how to verify the rotation worked. Supports Stripe, OpenAI, Anthropic, Google Cloud / AI Studio, GitHub, AWS, Slack, Supabase, Firebase, Postmark, and generic OAuth providers.
lictor-explain
Takes any security finding, error message, or jargon-heavy security advice and explains it in plain English. Use this when someone is confused by what /lictor-security-check found, or when they got a security warning from another tool and don't understand it.
lictor-fix-it
Applies the fixes recommended by /lictor-security-check, with the user's explicit permission for each change. Walks through findings one at a time, shows the proposed change, gets approval, applies, runs tests if available, and moves on. Some fixes (rotating leaked credentials) require the user to act outside Claude …
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.