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/pipecat-ai/pipecat/pr-descriptionnpx skills add pipecat-ai/pipecat --skill pr-descriptiongit 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/pr-description)<a href="https://agentmods.dev/skills/pipecat-ai/pipecat/pr-description"><img src="https://agentmods.dev/badge/skills/pipecat-ai/pipecat/pr-description.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.00014 | $0.00934 |
| Opus 5 | $0.00007 | $0.00467 |
| Sonnet 5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
pr-description 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update a GitHub pull request description based on the changes in the PR.
Arguments
/pr-description <PR_NUMBER> [--fixes <ISSUE_NUMBERS>]
PR_NUMBER(required): The pull request number to update--fixes(optional): Comma-separated issue numbers that this PR fixes (e.g.,--fixes 123,456)
Examples:
/pr-description 3534/pr-description 3534 --fixes 123/pr-description 3534 --fixes 123,456,789
Instructions
-
First, gather information about the PR:
- Use GitHub plugin to get PR details (title, current description, base branch)
- Use local git to get commits:
git log main..HEAD --oneline - Use local git to get the diff:
git diff main..HEAD - Parse any
--fixesargument for issue numbers
-
Check the existing PR description:
- If it already has a complete, accurate description that reflects the changes, do nothing
- If it's missing sections, incomplete, or outdated compared to the actual changes, proceed to update
- If it only has the template placeholder text, generate a full description
-
Analyze the changes:
- Understand the purpose of each commit
- Identify any breaking changes (API changes, removed features, behavior changes)
- Look for new features, bug fixes, refactoring, or documentation changes
- Collect issue numbers from:
- The
--fixesargument (if provided) - Commit messages (patterns like "Fixes #123", "Closes #456", "Resolves #789")
- The
-
Generate or update the PR description with these sections:
PR Description Format
Summary (always include)
Brief bullet points describing what changed and why. Focus on the purpose and impact, not implementation details.
## Summary
- Added X to enable Y
- Fixed bug where Z would happen
- Refactored W for better maintainability
Breaking Changes (include only if applicable)
Document any changes that affect existing users or APIs.
## Breaking Changes
- `ClassName.method()` now requires a `param` argument
- Removed deprecated `old_function()` - use `new_function()` instead
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 · 130 lines · 14 tokens per session scan A 16355f5387e2
pr-description is a skill published in the GitHub repository pipecat-ai/pipecat (15,180 stars, last pushed today), licensed BSD-2-Clause. It adds 14 tokens to every session and 934 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
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
start-quest
Find unblocked repository quests and start the user's choice. Use when the user invokes /start-quest, optionally with a base questline such as /start-quest vod, or asks what quest to work on next.
moss-search
Sub-10ms semantic search for Zo via Moss. Create indexes, add documents, and query them with semantic and keyword search. Use when users want to search through documents, knowledge bases, or any text content.
factory-rereview
Re-review a pull request after a push — reconcile the previous review against the new commits, look for new defects the push introduced, then a fresh pass over the whole PR, and finish with a verdict on the PR.
codemod-patterns
This guide helps AI agents efficiently create codemods with optimal performance and consistency.