Vexa is an open-source meeting transcription system whose bots join Google Meet, Microsoft Teams, and Zoom calls and stream speaker-labeled transcripts through an API. It is for teams that want meeting transcription and downstream knowledge processing either through hosted services or by running the stack themselves. The catalogue entries provide agents and instructions for working with Vexa.
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 Vexa-ai/vexa --skill setupgit clone --depth 1 https://github.com/Vexa-ai/vexaWrote 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/vexa-ai/vexa/setup)<a href="https://agentmods.dev/skills/vexa-ai/vexa/setup"><img src="https://agentmods.dev/badge/skills/vexa-ai/vexa/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/vexa-ai/vexa/setup"><img src="https://agentmods.dev/badge/skills/vexa-ai/vexa/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00062 | $0.00302 |
| Opus 5 | $0.00031 | $0.00151 |
| Sonnet 5 | $0.00012 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
vexa-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 4d 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
Vexa setup
The plugin needs one value: Vexa API key (vexa_api_key), and optionally the MCP URL (vexa_mcp_url).
- Hosted: sign in at https://vexa.ai/account and create a key. URL stays
https://api.cloud.vexa.ai/mcp. - Self-hosted:
make allin the Vexa repo prints a key when the stack is up; set the URL to your gateway's/mcp(Docker Compose defaulthttp://localhost:18056/mcp). Docs: https://docs.vexa.ai/deployment - The door: https://vexa.ai/connect mints a key and registers the server for the user's agent without this plugin; either path works.
Check the connection by calling whats_waiting. A 401 means the key is missing or wrong; a connection error usually means the URL points at a stack that is not up.
Do not paste keys into chat or files. Tell the user to enter the key in the plugin's settings (it is stored in the OS keychain).
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.
- 4d ago First seen · 17 lines · 62 tokens per session scan A 89eca0c1e3cd
vexa-setup is a skill published in the GitHub repository Vexa-ai/vexa (2,776 stars, last pushed 4d ago), licensed Apache-2.0. It adds 62 tokens to every session and 302 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-09-07.
Other skills, from other repositories
ai-meeting-notes
Messy notes → Clear action items. Instantly. Paste any meeting notes, transcript, or text. Get summaries, action items with owners and deadlines. Auto-saved, searchable, with integrated to-do tracking. No bot. No subscription. No setup.
ai-meeting-notes
Messy notes → Clear action items. Instantly. Paste any meeting notes, transcript, or text. Get summaries, action items with owners and deadlines. Auto-saved, searchable, with integrated to-do tracking. No bot. No subscription. No setup.
steno
Make the agent aware of the user's Steno meeting notes and able to pull them in on request. Steno (https://github.com/stenolabs/stenoai) records, transcribes, and summarizes meetings entirely on-device, storing each as a Markdown summary plus a transcript. This skill locates that store cross-platform (macOS, Windows…
granola-to-steno
Sync Granola meeting notes into Steno's file-based store. Reads recent meetings from the Granola MCP (titles, dates, participants, AI summaries, verbatim transcripts) and regenerates Steno's output/summary.md and transcripts/transcript.txt files in a target folder (e.g. an iCloud Drive directory). The operation is…
minutes-mirror
Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my…
minutes-debrief
Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.