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 agentmods add skills/livekit/agent-skills/livekit-agentsnpx skills add livekit/agent-skills --skill livekit-agentsgit clone --depth 1 https://github.com/livekit/agent-skillsWrote 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/livekit/agent-skills/livekit-agents)<a href="https://agentmods.dev/skills/livekit/agent-skills/livekit-agents"><img src="https://agentmods.dev/badge/skills/livekit/agent-skills/livekit-agents.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.02603 |
| Opus 5 | $0.00044 | $0.01301 |
| Sonnet 5 | $0.00018 | $0.00521 |
| Haiku 4.5 | $0.00009 | $0.00260 |
Grade A, and why
livekit-agents 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.
This is a copy
86% identical to livekit-skills — 162 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveKit Agents Development for LiveKit Cloud
This skill provides opinionated guidance for building voice AI agents with LiveKit Cloud. It assumes you are using LiveKit Cloud (the recommended path) and encodes how to approach agent development, not API specifics. All factual information about APIs, methods, and configurations must come from live documentation.
This skill is for LiveKit Cloud developers. If you're self-hosting LiveKit, some recommendations (particularly around LiveKit Inference) won't apply directly.
MANDATORY: Read This Checklist Before Starting
Before writing ANY code, complete this checklist:
- Read this entire skill document - Do not skip sections even if MCP is available
- Ensure LiveKit Cloud project is connected - You need
LIVEKIT_URL,LIVEKIT_API_KEY, andLIVEKIT_API_SECRETfrom your Cloud project - Set up documentation access - Use MCP if available, otherwise use web search
- Plan to write tests - Every agent implementation MUST include tests (see testing section below)
- Verify all APIs against live docs - Never rely on model memory for LiveKit APIs
This checklist applies regardless of whether MCP is available. MCP provides documentation access but does NOT replace the guidance in this skill.
LiveKit Cloud Setup
LiveKit Cloud is the fastest way to get a voice agent running. It provides:
- Managed infrastructure (no servers to deploy)
- LiveKit Inference for AI models (no separate API keys needed)
- Built-in noise cancellation, turn detection, and other voice features
- Simple credential management
Connect to Your Cloud Project
- Sign up at cloud.livekit.io if you haven't already
- Create a project (or use an existing one)
- Get your credentials from the project settings:
LIVEKIT_URL- Your project's WebSocket URL (e.g.,wss://your-project.livekit.cloud)LIVEKIT_API_KEY- API key for authenticationLIVEKIT_API_SECRET- API secret for authentication
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 · 286 lines · 88 tokens per session scan A 1d8f9c6ed8f2
livekit-agents is a skill published in the GitHub repository livekit/agent-skills (66 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 2,603 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to livekit-skills, differing in 162 lines, and is treated as a copy.
Other skills, from other repositories
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
80-livekit-agents-panaversity-agentfactory-1f8ecf89
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
80-livekit-agents-panaversity-agentfactory-1f8ecf89
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
81-pipecat
Create your Pipecat skill from official documentation, then learn to improve it throughout the chapter.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…