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-submitnpx skills add pipecat-ai/pipecat --skill pr-submitgit clone --depth 1 https://github.com/pipecat-ai/pipecatWhat 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.00335 |
| Opus 5 | $0.00007 | $0.00168 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
pr-submit 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 3d 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.
What it actually says
Submit the current changes as a GitHub pull request.
Instructions
-
Check the current state of the repository:
- Run
git statusto see staged, unstaged, and untracked changes - Run
git diffto see current changes - Run
git log --oneline -10to see recent commits
- Run
-
If there are uncommitted changes relevant to the PR:
- Ask the user if they want a specific prefix for the branch name (e.g.,
alice/,fix/,feat/) - Create a new branch based on the current branch
- Commit the changes using multiple commits if the changes are unrelated
- Ask the user if they want a specific prefix for the branch name (e.g.,
-
Run
/prose-review branchand fix anything it flags. Do this before pushing, while corrections are still cheap. -
Push the branch and create the PR:
- Push with
-uflag to set upstream tracking - Create the PR using
gh pr create
- Push with
-
After the PR is created:
- Run
/changelog <pr_number>to generate changelog files, then commit and push them - Run
/pr-description <pr_number>to update the PR description
Both skills review their own prose — no separate pass is needed here.
- Run
-
Return the PR URL to the user.
Commit messages are prose too — /prose-review reads diffs and so won't see them.
Read the messages in git log main..HEAD against the same standard before pushing.
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.
- 3d ago First seen · 37 lines · 14 tokens per session scan A 5eb237dbfb01
pr-submit is a skill published in the GitHub repository pipecat-ai/pipecat (15,103 stars, last pushed today), licensed BSD-2-Clause. It adds 14 tokens to every session and 335 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
after-production-release
What to tell the user right after publishing a noisy-coding release — derive the minimal refresh steps (image? plugin? per-session reloads?) from what actually changed and present them as a short spoken summary plus a bulleted console checklist. Use every time a release/tag is pushed, when the user asks "what do I…
creating-releases
How to cut a noisy-coding release — version bump, tag, GitHub release via gh, and above all HOW TO WRITE the release notes (agent-quotable Highlights, pain-first framing, upgrade notes derived from what changed). Repo-local skill for maintainers; use whenever asked to release, publish a version, or write release notes.
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…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.