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 NovaLux12/spotify-mcp-server --skill spotify-exhaustive-feature-sweepgit clone --depth 1 https://github.com/NovaLux12/spotify-mcp-serverWrote 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/novalux12/spotify-mcp-server/spotify-exhaustive-feature-sweep)<a href="https://agentmods.dev/skills/novalux12/spotify-mcp-server/spotify-exhaustive-feature-sweep"><img src="https://agentmods.dev/badge/skills/novalux12/spotify-mcp-server/spotify-exhaustive-feature-sweep/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/novalux12/spotify-mcp-server/spotify-exhaustive-feature-sweep"><img src="https://agentmods.dev/badge/skills/novalux12/spotify-mcp-server/spotify-exhaustive-feature-sweep.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.00034 | $0.02972 |
| Opus 5 | $0.00017 | $0.01486 |
| Sonnet 5 | $0.00007 | $0.00594 |
| Haiku 4.5 | $0.00003 | $0.00297 |
Grade A, and why
spotify-exhaustive-feature-sweep 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spotify Exhaustive Feature Sweep
When to Use
- Asked to do exhaustive/quantity-first sweep, beat N tools, find maximum candidates, or scout new features across Spotify domains (Catalog/Search/Browse, Playback/Queue/Devices, Playlists/Library/Social, Portability/Analytics/Resources/Prompts).
Procedure
-
Inventory current coverage per domain.
- Count
grep -rn "server\.tool\|registerTool" src --include="*.ts" | wc -lwith typed-search factory correction (545 raw including the 1 placeholder in catalog.ts → 545 - 1 + 7 = 551 server-wide as of v1.27.1; verify via livetools/list); per-domain files (playback.ts 16 + playbackext.ts 13 + queueops.ts 3 + scenes.ts 6 =38); readSPEC.md §9removed list andsrc/tools/*.tsfor existing endpoint coverage. - Completion: baseline tool count and removed-endpoint list recorded; endpoint→tool map drafted showing wrapped vs gap.
- Count
-
Inventory open work to avoid duplicates.
- List
git branch -aand diff each openswarm/*andfix/quota-*branch vs main; note PRs #243-255 tools (e.g., search_saved_tracks, export_listening_history, save_queue_as_playlist already open). - Completion: table of open branches → new tools noted; duplicates excluded from candidates.
- List
-
Enumerate every non-deprecated endpoint in each domain quantity-first.
- For assigned domain, list all live reads/writes (Search GET /search, Browse /browse/categories*, Catalog /tracks|albums|artists|shows|episodes|audiobooks|chapters, Player /me/player*, Playlists /playlists/{id}*, Follow /me/following, User /me, etc.); mark SPEC §9 deprecated as excluded (recommendations, audio-features, audio-analysis, related-artists, featured/new-releases).
- Completion: checklist with ≥1 candidate per live endpoint; deprecated explicitly marked excluded.
-
Expand each endpoint into 1-3 ergonomic wrappers.
- Apply expansion patterns: typed-search split (one endpoint ×7 type wrappers), saved-library filter family (/me/{type} + client filter), batch fan-out (catalog_batch_lookup mixed URIs, playlist set-algebra union/subtract/symmetric-difference), deep-dive bundles (category→playlists→peek, listening_session snapshot), market previews, include_groups shortcuts, portability sidecars (export/delta/snapshot-diff), analytics and resources/prompts.
- Completion: 20±2 ranked proposals per domain; each card has name, pitch, endpoint(s), params, use case, quota flag, ship bucket (P0/P1/P2/P3).
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.
- 8d ago Changed · +1 lines d75123205a64
- 11d ago First seen · 80 lines · 34 tokens per session scan A a53e3de63bfc
spotify-exhaustive-feature-sweep is a skill published in the GitHub repository NovaLux12/spotify-mcp-server (1 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 2,972 once invoked, about $0.0002 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
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
add-resource
Scaffold a new MCP resource definition. Use when the user asks to add a resource, expose data via URI, or create a readable endpoint.
add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.