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 manage-private-spotify-podcastsgit 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/manage-private-spotify-podcasts)<a href="https://agentmods.dev/skills/martin-gomola/spotify-mcp/manage-private-spotify-podcasts"><img src="https://agentmods.dev/badge/skills/martin-gomola/spotify-mcp/manage-private-spotify-podcasts/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/manage-private-spotify-podcasts"><img src="https://agentmods.dev/badge/skills/martin-gomola/spotify-mcp/manage-private-spotify-podcasts.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.00060 | $0.00759 |
| Opus 5 | $0.00030 | $0.00380 |
| Sonnet 5 | $0.00012 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
manage-private-spotify-podcasts 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 11d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage private Spotify podcasts
Use the external Save to Spotify CLI as the source of truth. This skill deletes individual private episodes only; it does not delete shows or mutate Spotify MCP playlists.
Preflight
- Check whether
save-to-spotifyis available onPATH. If it is missing, stop and direct the user to runmake codex-install-bundle, then start a new Codex task. - Run
save-to-spotify --json doctor. If its separate authorization is missing, follow the external$save-to-spotifysetup guidance before listing or deleting episodes. - Always use JSON mode. Never print, inspect, or transfer either tool's token.
Resolve the exact episode
- Run
save-to-spotify --json shows, then list episodes in the relevant show withsave-to-spotify --json episodes --show-id <exact-show-uri>. - Prefer an exact
spotify:episode:...URI supplied by the user. If the user supplied a title, resolve it only from the private episode listings. Present title, exact episode URI, show, and processing status before deletion. - If zero episodes or multiple episodes match, do not guess. Ask the user to select one exact URI.
- Never substitute a Spotify catalog episode, saved-library episode, or playlist item with a similar title.
- Allow deletion in any observed processing state, including
PROCESSING,NOT_READY,READY, orFAILED. Deletion does not require a readiness wait; surface the state so the user understands whether they are removing playable content or cleaning up a stuck upload.
Delete safely
- Treat episode deletion as irreversible. Unless the user's current message already names the
exact URI and explicitly commands its deletion, prefer the client's structured-choice UI. Put
the exact title,
spotify:episode:...URI, show, and current status in the confirmation question, then offer exactly two choices:- Delete episode - irreversible: this selection is the explicit delete confirmation and is bound to the exact displayed URI.
- Cancel: make no changes.
Do not ask for another confirmation after the user selects the delete choice. If structured
choices are unavailable, ask the user to reply with
delete <exact-episode-uri>as the portable fallback.
- Delete once with
save-to-spotify --json episodes delete <exact-episode-uri>. - Success from the write must report
status: deletedand the same exact episode ID. Preserve the original full URI in the user-facing result. - If the response is missing, times out, or is otherwise ambiguous, re-list the show's complete episode collection before considering any retry. Never repeat the delete blindly.
- Verify completion by re-listing every episode in the exact show and confirming that the exact episode URI is absent. Do not claim deletion from the write response alone.
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.
- 11d ago First seen · 60 lines · 60 tokens per session scan A fd5a97f4f51a
manage-private-spotify-podcasts is a skill published in the GitHub repository martin-gomola/spotify-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 759 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…
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…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.