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 create-private-spotify-podcastgit 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/create-private-spotify-podcast)<a href="https://agentmods.dev/skills/martin-gomola/spotify-mcp/create-private-spotify-podcast"><img src="https://agentmods.dev/badge/skills/martin-gomola/spotify-mcp/create-private-spotify-podcast/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/create-private-spotify-podcast"><img src="https://agentmods.dev/badge/skills/martin-gomola/spotify-mcp/create-private-spotify-podcast.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.00069 | $0.01259 |
| Opus 5 | $0.00034 | $0.00629 |
| Sonnet 5 | $0.00014 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
create-private-spotify-podcast 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 12d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a private Spotify podcast
Use the official external $save-to-spotify skill for production. Do not reproduce, replace, or
weaken its interview, chapter approval, preview, upload, timeline, cover, or readiness workflow.
Preflight
- Check whether
save-to-spotifyis available onPATH. If it is missing, stop cleanly and tell the user to runmake codex-install-bundle, then start a new Codex task. Do not install the companion directly from this skill. - Run
save-to-spotify --json doctorbefore sourcing or scripting. If authentication is missing, follow$save-to-spotifysetup guidance; its Spotify authorization is separate from Spotify MCP. - Version one supports only Kokoro. If doctor does not report Kokoro as available, explain that it
is a free local download of approximately 340 MB, request confirmation, then run
save-to-spotify tts setup --engine kokoro. Do not offer or require cloud TTS providers or API keys. Confirm Kokoro is available before scripting. - Inspect the proposed source before upload. Refuse content containing credentials, third-party personal data, or confidential business information. Ask the user for a redacted source instead; never copy sensitive values into scripts, logs, descriptions, timelines, or tool arguments.
- Confirm that the user owns the source or has the right to reproduce it as spoken audio. Do not upload third-party text or audio merely because the user supplied a copy.
Produce the episode
Invoke $save-to-spotify and follow its complete production pipeline. In particular, wait for the
user's plan approval and chapter approval, provide the required local preview before upload, keep
the episode private, set its timeline, and poll until the episode status is exactly READY.
Before asking for upload approval, explain that Spotify processes uploaded audio asynchronously.
The private show may display PROCESSING or NOT_READY for several minutes, occasionally longer;
that state means Spotify is still preparing the episode and does not mean the plugin failed.
Immediately after upload, report the exact episode URI and observed processing state. While polling,
give a short progress update when the state changes or about once per minute so the user is not left
guessing. Do not call processing a failure, re-upload, or attempt playlist placement unless Spotify
returns a terminal FAILED state; playlist placement still requires exact READY.
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.
- 12d ago First seen · 87 lines · 69 tokens per session scan A d704822694be
create-private-spotify-podcast is a skill published in the GitHub repository martin-gomola/spotify-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 1,259 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.