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/craftos-dev/craftbot/spotify-playernpx skills add CraftOS-dev/CraftBot --skill spotify-playergit clone --depth 1 https://github.com/CraftOS-dev/CraftBotWrote 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/craftos-dev/craftbot/spotify-player)<a href="https://agentmods.dev/skills/craftos-dev/craftbot/spotify-player"><img src="https://agentmods.dev/badge/skills/craftos-dev/craftbot/spotify-player.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.00017 | $0.00353 |
| Opus 5 | $0.00009 | $0.00177 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
spotify-player 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 2d 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.
This is a copy
95% identical to spotify-player — 32 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.
What it actually says
spogo / spotify_player
Use spogo (preferred) for Spotify playback/search. Fall back to spotify_player if needed.
Requirements
- Spotify Premium account.
- Either
spogoorspotify_playerinstalled.
spogo setup
- Import cookies:
spogo auth import --browser chrome
Common CLI commands
- Search:
spogo search track "query" - Playback:
spogo play|pause|next|prev - Devices:
spogo device list,spogo device set "<name|id>" - Status:
spogo status
spotify_player commands (fallback)
- Search:
spotify_player search "query" - Playback:
spotify_player playback play|pause|next|previous - Connect device:
spotify_player connect - Like track:
spotify_player like
Notes
- Config folder:
~/.config/spotify-player(e.g.,app.toml). - For Spotify Connect integration, set a user
client_idin config. - TUI shortcuts are available via
?in the app.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 35 lines · 17 tokens per session scan A 4a7a735fe86c
spotify-player is a skill published in the GitHub repository CraftOS-dev/CraftBot (378 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 353 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to spotify-player, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
turix-mac
Computer Use Agent (CUA) for macOS automation using TuriX. Use when you need to perform visual tasks on the desktop, such as opening apps, clicking buttons, or navigating UIs that don't have a CLI or API.
browser-control
Control web pages in an existing Chromium remote-debugging session with deterministic sagui commands or the browser-only AI Agent. Use when Claude Code needs to inspect tabs, observe semantic elements, navigate, click, type, send keys, scroll, or complete a browser goal through CDP without controlling native macOS UI…
agent-smoke-test
Run manual development checks for SwiftAutoGUI AI Agent actions through the local sagui CLI. Use when Claude or Codex needs to test app-control or Accessibility BasicAction generation on macOS.
macos-control
Control macOS GUI applications via mouse automation, keyboard input, screenshots, image recognition, and AppleScript execution. Use when you need to interact with macOS app UIs, take screenshots, click buttons, type text, scroll, drag, or locate images on screen.
artifact-storage-policy
管理 Codex 交付物的專案識別、Google Drive／GitHub 路由、檔名、儲存位置與回讀驗證；凡工作報告、外部保存、交付成果或新 repository 選擇涉及遠端儲存時使用。.
model-worker-routing
Route a task to the existing Ox Alpha worker only when the user explicitly names Ox Alpha; preserve normal Codex behavior for all other tasks.