Borrowing it
Nothing to install: this file belongs to pipecat-ai/skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pipecat-ai/skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/pipecat-ai/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/instructions/pipecat-ai/skills/claude-md)<a href="https://agentmods.dev/instructions/pipecat-ai/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/pipecat-ai/skills/claude-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.1 | $0.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
skills CLAUDE.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 6d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Repo Is
A Claude Code plugin marketplace (pipecat-skills) containing skills for building and deploying Pipecat applications. Published at pipecat-ai/skills on GitHub.
Architecture
This repo follows the Claude Code plugin marketplace pattern (same as anthropics/skills):
.claude-plugin/marketplace.json— Marketplace manifest. Defines plugins that each select skills from the sharedskills/directory.skills/<name>/SKILL.md— Each skill is a directory with aSKILL.mdfile containing frontmatter (name,description) and instructions that Claude follows when the skill is invoked.
Plugins
The marketplace exposes three plugins:
pipecat— General Pipecat development skills (e.g.init). Invoked as/pipecat:<skill>.pipecat-cloud— Pipecat Cloud deployment skills (e.g.deploy). Invoked as/pipecat-cloud:<skill>.pipecat-mcp-server— Pipecat MCP server skills (e.g.talk). Invoked as/pipecat-mcp-server:<skill>.
When adding a new skill, create skills/<name>/SKILL.md and add it to the appropriate plugin's skills array in marketplace.json.
Writing Skills
Skills are markdown files with instructions for Claude. Key conventions:
- Use AskUserQuestion for choices with a small fixed set of options (2-4 choices like yes/no, bot type, pipeline mode).
- For choices with many options (services, transports), show the full list as formatted text and let the user reply in chat.
- Skills that wrap CLI tools should use non-interactive/automation flags rather than interactive prompts, since Claude can't interact with TTY prompts.
- Use
--list-optionsstyle discovery commands when available to avoid hardcoding values that change over time.
Installation (for end users)
/plugin marketplace add pipecat-ai/skills
/plugin install pipecat@pipecat-skills
/plugin install pipecat-cloud@pipecat-skills
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.
- 6d ago First seen · 42 lines · 484 tokens per session scan A 38f33359be3c
skills CLAUDE.md is an instructions file published in the GitHub repository pipecat-ai/skills (25 stars, last pushed 1mo ago), licensed BSD-2-Clause. It adds 484 tokens to every session, about $0.0024 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.