Pipecat is an open-source Python framework for building real-time conversational agents that work with voice, video, images, and other media. It is for creating voice assistants, companions, business agents, and multi-agent systems from modular conversation pipelines.
Borrowing it
Nothing to install: this file belongs to pipecat-ai/pipecat. 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/pipecat/main/.claude/skills/changelog/SKILL.mdgit clone --depth 1 https://github.com/pipecat-ai/pipecatWrote 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/pipecat-ai/pipecat/changelog)<a href="https://agentmods.dev/skills/pipecat-ai/pipecat/changelog"><img src="https://agentmods.dev/badge/skills/pipecat-ai/pipecat/changelog.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.00013 | $0.00710 |
| Opus 5 | $0.00006 | $0.00355 |
| Sonnet 5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
changelog 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 7d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create changelog files for the important commits in this PR. The PR number is provided as an argument.
Instructions
-
Skip changelog for: documentation-only, internal refactoring, test-only, CI changes, and fixes to changes that have not shipped yet (the unreleased change's entry covers them — update that entry instead if the fix alters what it should say).
-
First, check what commits are on the current branch compared to main:
git log main..HEAD --oneline -
For each significant change, create a changelog file in the
changelog/folder using the format: Allowed types:added,changed,deprecated,removed,fixed,security,performance,other{PR_NUMBER}.added.md- for new features{PR_NUMBER}.added.2.md,{PR_NUMBER}.added.3.md- for additional entries of the same type{PR_NUMBER}.changed.md- for changes to existing functionality{PR_NUMBER}.fixed.md- for bug fixes{PR_NUMBER}.deprecated.md- for deprecations{PR_NUMBER}.removed.md- for removed features{PR_NUMBER}.security.md- for security fixes{PR_NUMBER}.performance.md- for performance improvements{PR_NUMBER}.other.md- for other changes
-
Each changelog file should at least contain a main single line starting with
-followed by a clear description of the change. No line wrapping. -
If the change is complicated, changelog files can have indented lines after the main line with additional details or code samples.
-
Use ⚠️ emoji prefix for breaking changes.
-
Write changes in user-facing terms first. Lead with what users of the framework will notice: new APIs, changed behavior, new parameters, fixed bugs they might have hit, etc. Implementation details (internal refactoring, how something is wired up under the hood) can be included as secondary context after the user-facing description, but should never be the only content of a changelog entry when there is a user-visible effect.
Good (user-facing first, implementation detail as context):
- Turn completion instructions now persist correctly across full context updates when using `system_instruction`. Previously they were injected as a context system message, which caused warning spam and didn't survive context updates.Bad (implementation detail only, no user-facing framing):
- Fixed turn completion instructions being injected as a context system message instead of using `system_instruction`.Ask yourself: "If I'm a developer building on Pipecat, what would I notice changed?" Start there.
-
Once the entries are written, run
/prose-review changelog/and fix anything it flags.
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.
- 7d ago First seen · 64 lines · 13 tokens per session scan A 6be67f500f45
changelog is a skill published in the GitHub repository pipecat-ai/pipecat (15,256 stars, last pushed today), licensed BSD-2-Clause. It adds 13 tokens to every session and 710 once invoked, about $0.0001 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 skills, from other repositories
pr-snapshot-release
Guide a Mastra maintainer through publishing an npm snapshot from a pull request or a specified repository branch. Use when asked to release, publish, or create a PR snapshot, branch snapshot, canary package build, or branch-specific npm tag. Performs source and branch preflight checks, requires confirmation before…
release
Cut a coordinated release of the voice-channel plugin — bump the version across all manifests, write a CHANGELOG entry, commit, push, tag, and publish a GitHub release. Use this skill whenever the user says "release", "cut a release", "version bump", "ship it", "publish", "do the release", "changelog and push", or…
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.