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/jamiew/spotify-mcp/spotify-api-watchnpx skills add jamiew/spotify-mcp --skill spotify-api-watchgit clone --depth 1 https://github.com/jamiew/spotify-mcpWrote 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/jamiew/spotify-mcp/spotify-api-watch)<a href="https://agentmods.dev/skills/jamiew/spotify-mcp/spotify-api-watch"><img src="https://agentmods.dev/badge/skills/jamiew/spotify-mcp/spotify-api-watch.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.00092 | $0.01109 |
| Opus 5 | $0.00046 | $0.00554 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
spotify-api-watch 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spotify API watch
Spotify ships breaking changes to the Web API with little notice and no RSS feed. This skill answers two questions: what did Spotify change, and does our server still work. Do both — a clean changelog does not mean nothing broke, because the regime flip described below happens silently.
1. Changelog sweep
uv run scripts/spotify_api_watch.py
Exit 1 means there are unreviewed entries. Spotify publishes no feed and no
changelog index, so this probes the predictable per-month URLs
(.../references/changes/<month>-<year>) and diffs against
scripts/spotify-api-seen.json.
For each NEW URL, fetch it and classify every item as:
- Breaks us — an endpoint spotipy calls, a field one of the Pydantic models in
src/spotify_mcp/fastmcp_server.pyrequires, or a path in the fallback layer at the bottom ofsrc/spotify_mcp/spotify_api.py. - Unlocks something — new capability worth a tool or a scope.
- Irrelevant — dashboard/quota/billing with no code impact.
Then re-run with --accept to record them as reviewed, and commit the updated JSON.
Only accept after you have actually read the entries.
2. Live conformance probe
The changelog tells you what Spotify announced; this tells you what our app actually gets. Requires the server connected as an MCP client — ask the user to reconnect if the tools are absent.
Run these and compare against the expectations:
| Call | Full/legacy regime | Restricted regime |
|---|---|---|
get_me |
returns email, country, product |
id only |
get_artist_info on any artist |
has followers, popularity |
both absent |
search_music with limit=20 |
can return >10 | capped at 10 |
save_tracks on one id |
succeeds via legacy /me/tracks |
succeeds via /me/library |
If the probe shows a flip to restricted, expect these to matter:
search_musicmax drops 50 → 10 (our schema still advertises 50).- Artist
followers/popularityand useremail/country/productvanish. Those fields are all optional on the Pydantic models, so they degrade rather than throw — keep them that way. - Playlist and library writes move to
/itemsand/me/library.with_fallbackinspotify_api.pyhandles this, but it caches per process, so the first call after a flip may fail before it settles. Watch for the "resolved to the legacy regime" log line to see which way it went.
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 · 86 lines · 92 tokens per session scan A c555fd5fe683
spotify-api-watch is a skill published in the GitHub repository jamiew/spotify-mcp (9 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,109 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other skills, from other repositories
social-spotify-card
Spotify Now Playing-style card with album art, progress bar, and playback controls, suited to video overlays or personal homepages.
social-spotify-card
Spotify Now Playing 风格卡: 专辑封面 + 进度条 + 播放控制, 适配视频叠加 / 个人主页.
spotatui-dj
Be the DJ for spotatui, the terminal music player, by driving its MCP server. Use whenever the user asks for music, asks you to DJ, wants tracks queued, played, skipped, or searched, asks what they have been listening to, or mentions spotatui.
github-triage
Use when touching anything on the GitHub side of christosk92/WaveeMusic — labels, milestones, the "Wavee" project board (Projects v2), issue forms / PR template, CONTRIBUTING / SECURITY, repo settings, Discussions, or triaging an issue or PR with gh. Every modifying gh call needs the user's explicit approval first.
wavee-sidebar
Use when changing anything in Wavee's left sidebar — the three designs (Classic / Library V3 / Wavee Curated), the one SidebarPane renderer, the layout document + reducer + templates, the projection/binder/planner data pipeline, sidebar-layout.json persistence, the full-page customizer, pins, or the extension-platform…
releasing
Use when cutting, publishing, or troubleshooting a Wavee MSIX release — the local ops/release/wavee-release.ps1 runbook (no CI job), the wavee-v tag and the rolling wavee-stable update feed, building/signing the NativeAOT MSIX, Azure Trusted Signing failures (Invalid tenant id, SignerSign 0x80004005, publisher…