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/.claude/skills/update/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/update)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/update"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/update/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/update"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/update.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.00049 | $0.01136 |
| Opus 5 | $0.00024 | $0.00568 |
| Sonnet 5 | $0.00010 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
update 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update - Restart Vellum (with Smart Branch Handling)
Restart the Vellum assistant and gateway services with branch-aware git behavior.
Arguments
The user may pass $ARGUMENTS to control branch behavior:
| Invocation | Behavior |
|---|---|
/update (no args, on main) |
Pull latest from origin/main (default) |
/update (no args, on a feature branch) |
Skip git ops - restart with the current checkout |
/update <branch> |
Check out that branch, pull if it has a remote |
/update --pull |
Force pull on whatever branch you're currently on |
Steps
-
Ensure Bun is on PATH:
export PATH="$HOME/.bun/bin:$PATH" -
Preflight snapshot - capture current state before making changes:
vellum ps -
Quiesce with
vellum sleep- stop assistant and gateway processes. This is directory-agnostic and stops processes globally regardless of CWD:vellum sleep || true -
Verify stopped - run
vellum psand confirm no running processes. Ifvellum psshows processes still running, run fallback cleanup to force-kill them:vellum psFallback cleanup if
vellum psconfirms processes are still running:pkill -x "vellum-assistant" || true pkill -f "gateway/src/index" || true lsof -ti :7830 | xargs kill -9 2>/dev/null || true lsof -ti :7821 | xargs kill -9 2>/dev/null || trueAfter fallback cleanup, run
vellum psagain to confirm all processes are stopped. -
Smart branch handling - determine what git operations (if any) to perform:
CURRENT=$(git branch --show-current) GIT_OPS_RAN=falseCase A -
--pullflag: Force pull on the current branch.if [[ "$ARGUMENTS" == "--pull" ]]; then git pull GIT_OPS_RAN=true fiCase B - Explicit branch name provided: Check out the requested branch, pulling if possible. Before checking out, verify the working tree is clean - if there are uncommitted changes, stop and warn the user rather than silently losing work. Do NOT stash automatically.
if [[ -n "$ARGUMENTS" && "$ARGUMENTS" != "--pull" ]]; then if ! git diff --quiet || ! git diff --cached --quiet; then echo "ERROR: Uncommitted changes detected. Commit or stash them before switching branches." # Stop and report the error to the user. Do not proceed. fi git checkout "$ARGUMENTS" git pull origin "$ARGUMENTS" 2>/dev/null || true GIT_OPS_RAN=true fi
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 · 125 lines · 49 tokens per session scan A 35604b556c32
update is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,214 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,136 once invoked, about $0.0002 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
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
engine-conflict-resolve
Ask Sutando to resolve a conflicted update of a Sutando checkout. When pulling the latest release/main conflicts with local changes, Sutando reproduces the merge in a scratch git worktree, resolves the conflicts there, proposes the resolution to the owner, and fast-forwards the live checkout only after explicit…
submit-use-case
OSS-facing channel to share a Sutando use case with the community. Opens a labeled GitHub issue on sonichi/sutando and (CLA-gated) a PR adding docs/community-use-cases/ .md. Validates outcome-framed titles with the same checker as add-use-case. Default: both; flags --issue-only / --pr-only opt out.
release
Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.