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 elevenlabs-voicegit 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/elevenlabs-voice)<a href="https://agentmods.dev/skills/vellum-ai/vellum-assistant/elevenlabs-voice"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/elevenlabs-voice/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/elevenlabs-voice"><img src="https://agentmods.dev/badge/skills/vellum-ai/vellum-assistant/elevenlabs-voice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, 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 Supply Chain · line 111 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Supply Chain · line 118 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- medium Data Exfiltration · line 111 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 118 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00031 | $0.02317 |
| Opus 5 | $0.00015 | $0.01158 |
| Sonnet 5 | $0.00006 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade C, and why
elevenlabs-voice scanned grade C with 2 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
To collect the API key securely: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.elevenlabs.io/v2/voices?category=premade&page_size=50" \ How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
ElevenLabs provides text-to-speech voices for both in-app TTS and phone calls. Change the voice with the voice_config_update tool — it writes the voice to whichever TTS provider is currently active and pushes to the macOS app via SSE in one call:
voice_config_update setting="tts_voice_id" value="<voice-id>"
The voice lives under the active provider, not always ElevenLabs. The config key depends on
services.tts.provider:elevenlabs→services.tts.providers.elevenlabs.voiceId,vellum(managed) →services.tts.providers.vellum.model,deepgram→services.tts.providers.deepgram.model. Thevoice_config_updatetool (and theassistant tts voice <id>CLI command) handle this routing for you. Do NOTassistant config set services.tts.providers.elevenlabs.voiceId ...blindly — on a managed (vellum) assistant that field is ignored, so the write "succeeds" but the voice never changes. See Setting the voice for the CLI fallback.The tables below apply when the active provider is
elevenlabs(BYO key) or managedvellum. On managed assistants they are the only ElevenLabs voices — the platform bills per rate-carded model and rejects anything else at synthesis (the write succeeds but the voice fails on the next turn), so don't offer library or cloned voices unless theelevenlabsprovider is active with its own API key. With a BYO key (setup below) andelevenlabsactive, any voice id works. Other BYO TTS providers (deepgram,xai,fish-audio, …) use their own voice/model identifiers — never write an ElevenLabs voice id to them; see Getting to an ElevenLabs voice from another provider.
Getting to an ElevenLabs voice from another provider
Check the active provider first: assistant config get services.tts.provider.
- Already on managed
vellum? No provider change needed. The managed platform supports both ElevenLabs and Deepgram voices —services.tts.providers.vellum.modelaccepts either an ElevenLabs voice id or an Aura model id, so switching between them is just anothervoice_config_updatecall. - On a BYO provider (e.g.
deepgram) and the user wants an ElevenLabs voice? Two options — ask which they prefer. Switch with thevoice_config_updatetool, not rawassistant config set— the tool validates the switch (e.g. rejectsvellumwhen no platform connection exists, which a raw config write would leave silently broken):- Switch to managed
vellum(voice_config_update setting="tts_provider" value="vellum") — no ElevenLabs key needed; requires a platform connection and bills managed credits. Bonus: they keep access to both the ElevenLabs and Deepgram catalogs. - Switch to BYO
elevenlabs(voice_config_update setting="tts_provider" value="elevenlabs") — requires an ElevenLabs API key (setup below); usage bills their ElevenLabs account directly.
- Switch to managed
What ships with it
1 file 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.
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 · 168 lines · 31 tokens per session scan C f5b305d5b0d5
elevenlabs-voice is a skill published in the GitHub repository vellum-ai/vellum-assistant (1,234 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,317 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, 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
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.