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 skills add CherryHQ/cherry-studio --skill issue-reportergit 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/issue-reporter)<a href="https://agentmods.dev/skills/cherryhq/cherry-studio/issue-reporter"><img src="https://agentmods.dev/badge/skills/cherryhq/cherry-studio/issue-reporter.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.1 | $0.00073 | $0.00589 |
| Opus 5 | $0.00036 | $0.00295 |
| Sonnet 5 | $0.00015 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
issue-reporter 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 7d 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.
- 7d ago First seen · 42 lines · 73 tokens per session scan A 704557ac405a
issue-reporter is a skill published in the GitHub repository CherryHQ/cherry-studio (51,494 stars, last pushed today), licensed AGPL-3.0. It adds 73 tokens to every session and 589 once invoked, about $0.0004 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
superpowers-finishing-a-development-branch
Branch finished, tests green? Load first to merge, PR, or clean up.
superpowers-using-git-worktrees
Feature work needing an isolated workspace, or executing a plan? Load first.
superpowers-sync-upstream
Sync this port with upstream obra/superpowers or Reasonix main-v2: detect drift, re-port, bench-gate.
vibe-cherry-pick-integration
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
vibe-pre-commit-audit
Scans staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.