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 martin-gomola/spotify-mcp --skill setup-spotify-mcpgit clone --depth 1 https://github.com/martin-gomola/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/martin-gomola/spotify-mcp/setup-spotify-mcp)<a href="https://agentmods.dev/skills/martin-gomola/spotify-mcp/setup-spotify-mcp"><img src="https://agentmods.dev/badge/skills/martin-gomola/spotify-mcp/setup-spotify-mcp/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/martin-gomola/spotify-mcp/setup-spotify-mcp"><img src="https://agentmods.dev/badge/skills/martin-gomola/spotify-mcp/setup-spotify-mcp.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.00055 | $0.00336 |
| Opus 5 | $0.00028 | $0.00168 |
| Sonnet 5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
setup-spotify-mcp 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 10d 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.
What it actually says
Set up Spotify MCP
Complete all reversible technical work yourself and ask only for the Spotify client ID or browser approval that cannot be obtained locally.
- Locate the checkout from
SPOTIFY_MCP_REPO, defaulting to~/dev/spotify-mcp. - Ensure the ignored
.envfile containsSPOTIFY_CLIENT_ID; copy.env.examplewhen needed. - If no client ID is configured, explain how to create a Spotify Web API app and register exactly
http://127.0.0.1:8888/callback. Ask for the client ID only; PKCE needs no client secret. - Run
make setup. Let the user approve the Spotify browser page when authentication is missing, then verify the reported account is ready. - For Codex installation or repair, run
make codex-installand tell the user to start a new task. Codex owns the stdio process; do not leavemake runopen. Usemake runonly for standalone manual startup, where the foreground terminal intentionally remains attached. - Report the concrete result. Never paste tokens, authorization codes, or credential-file content.
Spotify Development Mode requires the app owner to have Premium and currently limits allow-listed users. Playback additionally needs Spotify open on an available device.
What ships with it
3 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.
- 10d ago First seen · 24 lines · 55 tokens per session scan A 140ec1b5fea7
setup-spotify-mcp is a skill published in the GitHub repository martin-gomola/spotify-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 336 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-31.
Other skills, from other repositories
spotify-mcp-doctor
Diagnose and repair NovaLux12/spotify-mcp-server failures — auth, permissions, devices, rate limits, OpenClaw wiring. Use when Spotify tool calls fail or setup stalls.
spotify-exhaustive-feature-sweep
Exhaustive feature sweep across Spotify domains — enumerate all endpoints into quantity-first tool proposals with quota flags and batched GitHub logging.
spotify-mcp-competitor-comparison
Answer "is our MCP standard/conformant" or "do others offer more" questions with in-repo protocol evidence, then web research.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…