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 instructions/pipecat-ai/voice-ui-kit/agents-mdgit clone --depth 1 https://github.com/pipecat-ai/voice-ui-kitWrote 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/instructions/pipecat-ai/voice-ui-kit/agents-md)<a href="https://agentmods.dev/instructions/pipecat-ai/voice-ui-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/pipecat-ai/voice-ui-kit/agents-md.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.01434 | $0.01434 |
| Opus 5 | $0.00717 | $0.00717 |
| Sonnet 5 | $0.00287 | $0.00287 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
voice-ui-kit AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidelines for AI agents and human contributors working on Voice UI Kit.
Project Overview
Voice UI Kit (@pipecat-ai/voice-ui-kit) is a React component library for building voice AI applications with Pipecat. It provides components, hooks, and template apps for real-time voice, video, and AI interactions.
- NPM:
@pipecat-ai/voice-ui-kit - Docs: https://voiceuikit.pipecat.ai
- License: BSD-2-Clause
Repository Structure
This is a pnpm monorepo ([email protected], Node >=18).
package/ Main library (publishable to NPM)
src/ Library source code (React components, hooks, CSS)
dist/ Build output (gitignored)
tsup.config.ts Build config (tsup — ESM + CJS + .d.ts)
package.json Version source of truth
CHANGELOG.md Auto-generated changelog (managed by Release Please)
docs/ Documentation site (private, Fumadocs/Next.js)
examples/ Example applications (private)
01-console/
02-components/
03-tailwind/
04-vite/
05-themes/
scripts/ Build scripts (CSS post-processing)
.github/workflows/ CI/CD workflows
Key Configuration Files
| File | Purpose |
|---|---|
package.json (root) |
Monorepo config, shared devDependencies, lint-staged |
package/package.json |
Library package — version, exports, peer dependencies |
release-please-config.json |
Release Please configuration |
.release-please-manifest.json |
Current version tracking (managed by Release Please) |
.commitlintrc.json |
Conventional commit rules |
pnpm-workspace.yaml |
Workspace definitions |
Development Workflow
Setup
pnpm install # Install all dependencies (also sets up Husky hooks)
pnpm build # Build the library
Local Development
pnpm dev # Component storybook (Ladle) for package/
pnpm dev:docs # Documentation site (Next.js)
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 · 174 lines · 1,434 tokens per session scan A de8b6da034b8
voice-ui-kit AGENTS.md is an instructions file published in the GitHub repository pipecat-ai/voice-ui-kit (408 stars, last pushed 9d ago), licensed BSD-2-Clause. It adds 1,434 tokens to every session, about $0.0072 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.