Borrowing it
Nothing to install: this file belongs to NovaLux12/spotify-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NovaLux12/spotify-mcp-server/main/CLAUDE.mdgit 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/instructions/novalux12/spotify-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/novalux12/spotify-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/novalux12/spotify-mcp-server/claude-md.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.1 | $0.01193 | $0.01193 |
| Opus 5 | $0.00596 | $0.00596 |
| Sonnet 5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
spotify-mcp-server CLAUDE.md 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 7d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpotifyMCP — Claude Code Rules
You are helping build an MCP server that wraps the Spotify Web API. Follow these rules at all times.
Spotify API Reference
Always refer to the official Spotify OpenAPI specification for endpoint paths, parameters, and response schemas:
- OpenAPI schema: https://developer.spotify.com/reference/web-api/open-api-schema.yaml
- API reference: https://developer.spotify.com/documentation/web-api/reference
Do not guess endpoint paths, query parameter names, or response field names. Look them up.
Authorization
- Use Authorization Code with PKCE for all user-specific data (the standard flow for this MCP server).
- The Authorization Code flow (with client secret on a secure backend) is also acceptable if a backend component is added.
- Use Client Credentials only for non-user, public catalog data (no user context).
- Never use the Implicit Grant flow — it is deprecated by Spotify.
Redirect URIs
- Always use
https://redirect URIs in production. - For local development, use
http://127.0.0.1(nothttp://localhost). - Never use wildcard URIs.
- Reference: https://developer.spotify.com/documentation/web-api/concepts/redirect_uri
OAuth Scopes
- Request only the minimum scopes required for the feature being built.
- Do not request broad scopes preemptively "just in case."
- Reference: https://developer.spotify.com/documentation/web-api/concepts/scopes
Token Management
- Store tokens securely (local file with restricted permissions, never in source control).
- Never expose the Client Secret in client-side or committed code.
- Always implement token refresh so the app does not break when access tokens expire (they expire after 1 hour).
- Reference: https://developer.spotify.com/documentation/web-api/tutorials/refreshing-tokens
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.
- 7d ago First seen · 96 lines · 1,193 tokens per session scan A 1c503532a8a4
spotify-mcp-server CLAUDE.md is an instructions file published in the GitHub repository NovaLux12/spotify-mcp-server (1 stars, last pushed today), licensed MIT. It adds 1,193 tokens to every session, about $0.0060 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.