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/cleanupnpx skills add pipecat-ai/pipecat --skill cleanupgit 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/cleanup)<a href="https://agentmods.dev/skills/pipecat-ai/pipecat/cleanup"><img src="https://agentmods.dev/badge/skills/pipecat-ai/pipecat/cleanup.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.00017 | $0.01737 |
| Opus 5 | $0.00009 | $0.00869 |
| Sonnet 5 | $0.00003 | $0.00347 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
cleanup 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Cleanup Skill
The Code Cleanup Skill reviews, refactors, and documents code changes in your current branch, ensuring alignment with Pipecat's architecture, coding standards, and example patterns. It focuses on readability, correctness, performance, and consistency, while avoiding breaking changes.
Skill Overview
This skill analyzes all changes introduced in your branch and performs the following actions:
- Analyze Branch Changes
- Review uncommitted changes and outgoing commits
- Refactor for Readability
- Improve clarity, naming, structure, and modern Python usage
- Enhance Performance
- Identify safe, conservative optimization opportunities
- Add Documentation
- Apply Pipecat-style, Google-format docstrings
- Ensure Pattern Consistency
- Match existing Pipecat services, pipelines, and examples
- Validate Examples
- Ensure examples follow foundational patterns (e.g.
07-interruptible.py)
- Ensure examples follow foundational patterns (e.g.
Usage
Invoke the skill using any of the following commands:
- "Clean up my branch code"
- "Refactor the changes in my branch"
- "Review and improve my branch code"
/cleanup
What This Skill Does
1. Analyze Branch Changes
The skill retrieves all uncommitted changes and outgoing commits to understand:
- New files added
- Modified files
- Code additions and deletions
- Overall scope and intent of changes
2. Code Refactoring
Readability Improvements
- Replace tuples with named classes or dataclasses
- Improve variable, method, and class naming
- Extract complex logic into well-named helper methods
- Add missing type hints
- Simplify nested or complex conditionals
- Replace deprecated methods and features
- Normalize formatting to match Pipecat style
Performance Enhancements
- Identify inefficient loops or repeated work
- Suggest appropriate data structures
- Optimize async workflows and I/O
- Remove redundant operations
Performance changes are conservative and non-breaking.
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 · 326 lines · 17 tokens per session scan A 4f419ba49000
cleanup is a skill published in the GitHub repository pipecat-ai/pipecat (15,180 stars, last pushed today), licensed BSD-2-Clause. It adds 17 tokens to every session and 1,737 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
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
spreadsheet-agent
Authoring playbook for building agents that read or write tabular data — Google Sheets, Microsoft Excel, CSV, Airtable, Notion databases, or any spreadsheet. Use this when the user wants an agent that updates rows, reads cells, computes totals, generates reports from sheets, syncs data between spreadsheets, or…
generic-assistant
Fallback authoring playbook for building general-purpose personal assistant agents that do not fit a more specific archetype. Use this only after checking the other archetype skills (coding, spreadsheet, research, customer-support, content-writer, ops-automation). Examples include summarizing emails, drafting short…
convert-voice
Apply The Donahoe Voice Rules: sentence mechanics, word choices, structural moves, and the Bullshit Filter as a checklist. Operating system for every piece of copy - every headline, email, sales page, ad - passes through these non-negotiable rules. Use when a draft exists in some voice (yours, AI default…
langchain_patterns
Implement Retrieval-Augmented Generation (RAG) systems with LangChain4j. Build document ingestion pipelines, embedding stores, vector search strategies, and knowledge-enhanced AI applications. Use when creating question-answering systems over document collections or AI assistants with external knowledge bases.
langchain_patterns
Implement Retrieval-Augmented Generation (RAG) systems with LangChain4j. Build document ingestion pipelines, embedding stores, vector search strategies, and knowledge-enhanced AI applications. Use when creating question-answering systems over document collections or AI assistants with external knowledge bases.