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 agent-notesgit 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/agent-notes)<a href="https://agentmods.dev/skills/cherryhq/cherry-studio/agent-notes"><img src="https://agentmods.dev/badge/skills/cherryhq/cherry-studio/agent-notes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cherryhq/cherry-studio/agent-notes"><img src="https://agentmods.dev/badge/skills/cherryhq/cherry-studio/agent-notes.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00922 |
| Opus 5.5 | $0.00020 | $0.00369 |
| Sonnet 5.5 | $0.00010 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
agent-notes 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.
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.
- yesterday First seen · 49 lines · 51 tokens per session scan A e6c1959b86be
agent-notes is a skill published in the GitHub repository CherryHQ/cherry-studio (52,733 stars, last pushed today), licensed AGPL-3.0. It adds 51 tokens to every session and 922 once invoked, about $0.0002 per session on Opus 5.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-10-18.
Other skills, from other repositories
vibe-workstream-orchestration
Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording…
vibe-requirements-validator
Validates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.
vibe-scope-guard
Detects and redirects scope creep during implementation — unrequested features, drive-by refactors, premature abstraction, and over-engineering. Use while implementing, especially when a change is growing beyond the original request.
vibe-iteration-review
Performs end-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.