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-oauth-integrationsgit 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-oauth-integrations)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/vellum-oauth-integrations"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/vellum-oauth-integrations/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-oauth-integrations"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/vellum-oauth-integrations.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.00025 | $0.01237 |
| Opus 5 | $0.00013 | $0.00619 |
| Sonnet 5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
vellum-oauth-integrations 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 8d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using OAuth Integrations
Integrating with a third-party software via OAuth is typically used to perform actions on behalf of the user. It involves having the user log in using their own credentials, specifying the scopes that they want to provide, and then afterwards, API requests can be made on their behalf.
Important: Avoid reaching for an OAuth integration if your intent is to act as yourself rather than as your user.
The Assistant OAuth CLI
You are provided with the assistant oauth CLI for performing all necessary oauth-related actions.
Important: When in doubt how a command works or how to do something, read the references at the bottom. Never guess at how the CLI works. Read references and use the --help flag for any command you're about to run.
Viewing Available OAuth Providers
Vellum assistants can natively integrate with any application that supports OAuth 2.0. Many OAuth providers come pre-configured and ready to use. You can view them by running:
assistant oauth providers list
You can also search for specific providers. Here's an example that searches for the "google" provider:
assistant oauth providers list --provider-key google
Managed vs Your-Own Mode
All providers support "your-own" mode and some support "managed" mode.
Default: Managed Mode
"managed" mode relies on a first-class integration with the Vellum Platform. Managed mode is typically easier to set up and get going, often only requiring the user to log in with no additional configuration needed before they can begin using the integration. Managed mode is the recommended method for most users, especially those that are less technical or newer to their Vellum assistant.
When a task needs a managed OAuth connection, present it in chat with ui_show using surface_type: "oauth_connect" instead of sending the user to Settings or trying to open the OAuth flow from shell. See Connecting Accounts for the exact surface shape.
What ships with it
33 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.
- references/CONFIGURING_APPLICATIONS.md 4.9 KB
- references/CONNECTING_ACCOUNTS.md 6.1 KB
- references/MAKING_REQUESTS.md 7.3 KB
- references/provider-app-setups/airtable-path-b.md 3.1 KB
- references/provider-app-setups/airtable.md 3.5 KB
- references/provider-app-setups/asana-path-b.md 2.8 KB
- references/provider-app-setups/asana.md 3.4 KB
- references/provider-app-setups/discord-path-b.md 3.5 KB
- references/provider-app-setups/discord.md 4.4 KB
- references/provider-app-setups/dropbox-path-b.md 3.1 KB
- references/provider-app-setups/dropbox.md 4.1 KB
- references/provider-app-setups/figma-path-b.md 4.2 KB
- references/provider-app-setups/figma.md 6.1 KB
- references/provider-app-setups/github-path-b.md 2.6 KB
- references/provider-app-setups/github.md 3.7 KB
- references/provider-app-setups/google-path-b.md 7.1 KB
- references/provider-app-setups/google.md 11 KB
- references/provider-app-setups/hubspot-path-b.md 3.3 KB
- references/provider-app-setups/hubspot.md 4.4 KB
- references/provider-app-setups/linear-path-b.md 2.7 KB
- references/provider-app-setups/linear.md 4.0 KB
- references/provider-app-setups/notion-non-admin.md 1.8 KB
- references/provider-app-setups/notion-path-b-public.md 3.2 KB
- references/provider-app-setups/notion-path-b.md 3.2 KB
- references/provider-app-setups/notion.md 6.1 KB
- references/provider-app-setups/spotify-path-b.md 2.8 KB
- references/provider-app-setups/spotify.md 4.2 KB
- references/provider-app-setups/todoist-path-b.md 2.6 KB
- references/provider-app-setups/todoist.md 2.9 KB
- references/provider-app-setups/twitter-path-b.md 3.5 KB
- references/provider-app-setups/twitter.md 6.4 KB
- references/REGISTERING_PROVIDERS.md 2.1 KB
- references/UPDATING_SCOPES.md 2.3 KB
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.
- 8d ago First seen · 121 lines · 25 tokens per session scan A 2db823fa0bb4
vellum-oauth-integrations is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,225 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,237 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
web-deserialization
Insecure deserialization to RCE for web apps. Use when the app deserializes attacker-controlled data - cookies/tokens/hidden fields/params that are serialized blobs, VIEWSTATE, Java/PHP/.NET/Python/Node apps. Triggers - base64 starting rO0AB or hex AC ED 00 05 (Java), PHP serialize O-prefix, VIEWSTATE, python pickle…
ms365-connect
Connect to Microsoft 365 (OneDrive, Outlook mail, Calendar, Teams) via Microsoft Graph using the open-source python-o365 (O365) library. Use when the user wants to list/download OneDrive files, read or send Outlook email, list calendar events, or post a message to a Teams channel from a Sutando workflow.
calling-llms
Use when sending chat completions through liter-llm and routing to a specific provider via the provider/model prefix. Covers the chat call shape, provider routing, modelhint, message roles, and error categories.
running-the-proxy
Use when running the liter-llm api OpenAI-compatible gateway — virtual keys, per-key rate limits, budgets, cost tracking, and model routing. Covers the TOML config and the 22 REST endpoints.
streaming-responses
Use when streaming tokens incrementally from an LLM via liter-llm over SSE or async iterators. Covers chatstream, delta handling, and null-content chunks.
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…