Cherry Studio is a desktop application for Windows, Mac, and Linux that brings together conversations with multiple language-model providers, local models, configurable assistants, document processing, and connected tools. It is for people who want one workspace for AI chat, productivity, and agent tasks, and the catalogue add-ons add skills, agents, instructions, and plugins for that workflow.
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/cherryhq/cherry-studio/cherry-pr-testnpx skills add CherryHQ/cherry-studio --skill cherry-pr-testgit clone --depth 1 https://github.com/CherryHQ/cherry-studioWrote 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/cherryhq/cherry-studio/cherry-pr-test)<a href="https://agentmods.dev/skills/cherryhq/cherry-studio/cherry-pr-test"><img src="https://agentmods.dev/badge/skills/cherryhq/cherry-studio/cherry-pr-test.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.00057 | $0.01150 |
| Opus 5 | $0.00028 | $0.00575 |
| Sonnet 5 | $0.00011 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
cherry-pr-test 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 5d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 5d ago First seen · 162 lines · 57 tokens per session scan A e77cfc1399d1
cherry-pr-test is a skill published in the GitHub repository CherryHQ/cherry-studio (51,442 stars, last pushed today), licensed AGPL-3.0. It adds 57 tokens to every session and 1,150 once invoked, about $0.0003 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
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
dev-workflow
Skill "dev-workflow" from xstongxue/best-skills, covering 开发流程五步法, 使用时机, step 1：识别当前步骤, step 2：收集输入 and step 3：执行、输出与自动落盘.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.