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/xx5921/pipecat-mcp-server/deploynpx skills add xx5921/pipecat-mcp-server --skill deploygit clone --depth 1 https://github.com/xx5921/pipecat-mcp-serverWhat 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.00010 | $0.01905 |
| Opus 5 | $0.00005 | $0.00953 |
| Sonnet 5 | $0.00002 | $0.00381 |
| Haiku 4.5 | $0.00001 | $0.00191 |
Grade A, and why
deploy 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 yesterday.
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.
This is a copy
86% identical to deploy — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy an agent to Pipecat Cloud. This skill walks through the full deployment process interactively, confirming each step with the user.
Arguments
/deploy [--config <PATH>] [--env <PATH>]
--config(optional): Path topcc-deploy.toml. Defaults topcc-deploy.tomlin the current directory.--env(optional): Path to.envfile for creating secrets. If not provided, the skill will look for a.envfile in the same directory as the config file.
Examples:
/deploy/deploy --config examples/mybot/pcc-deploy.toml/deploy --config examples/mybot/pcc-deploy.toml --env examples/mybot/.env
Prerequisites
Before starting, verify these prerequisites and inform the user about any that are missing:
-
Pipecat Cloud CLI: Check if
pcis installed by runningpc --version. If not installed, tell the user to install it withuv tool install pipecat-ai-cliand stop. -
Pipecat Cloud authentication: Check if
pc cloud auth whoamisucceeds. If not authenticated, runpc cloud auth login --headlessas a background task, then read the output file to extract the URL and six-digit code. Share both with the user so they can authenticate in their browser. Wait for the background task to complete before proceeding. -
Configuration file: Read the
pcc-deploy.tomlfile (from--configargument or current directory). If it doesn't exist, tell the user they need apcc-deploy.tomland stop. Parse and display the configuration to the user (agent_name, image, secret_set, etc.).
If any prerequisite fails, stop and clearly explain what needs to be fixed. Do not proceed to the next steps.
Deployment Method
After prerequisites pass, ask the user how they want to deploy using AskUserQuestion:
- Cloud Build (Recommended): Pipecat Cloud builds your Docker image from source. No local Docker required.
- Self-managed image: Build and push your own Docker image from your machine, then deploy.
Important: Running Commands
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.
- yesterday First seen · 164 lines · 10 tokens per session scan A 21c0d5155852
deploy is a skill published in the GitHub repository xx5921/pipecat-mcp-server (0 stars, last pushed 2mo ago), licensed BSD-2-Clause. It adds 10 tokens to every session and 1,905 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to deploy, differing in 35 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.