Borrowing it
Nothing to install: this file belongs to WisetechySolutions/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/WisetechySolutions/spotify-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/WisetechySolutions/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/wisetechysolutions/spotify-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/wisetechysolutions/spotify-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/wisetechysolutions/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.00493 | $0.00493 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
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 6d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project instructions for Claude Code sessions.
Project Overview
Spotify MCP Server — lets Claude create Spotify playlists through natural language. Website at playmcp.dev (Astro 6, Cloudflare Pages).
Commands
npm run build # Compile TypeScript
npm test # Run 99 tests (vitest)
npm run dev # TypeScript watch mode
cd website && npm run build # Build Astro site
Architecture
src/
├── auth/ # PKCE OAuth, token store, callback server
├── spotify/ # API client, search, playlists, playlist-items
├── tools/ # MCP tool registration + Zod schemas
├── prompts/ # Creative playlist prompt templates
├── resources/ # User profile, auth status
└── utils/ # Config, crypto, error handler, rate limiter
website/ # Astro 6 companion site
Rules
- Security first. Defense in depth on everything. Validate inputs, sanitize outputs, never leak tokens in errors.
- No Spotify data caching. API responses are ephemeral — never persist beyond the current request. This is a compliance requirement.
- All API responses must go through
safeParseJsonResponse. Never use rawresponse.json(). - All string inputs must use the
safeStringZod refinement. Rejects null bytes and control characters. - Test everything. New features need tests. Currently at 99 tests across 9 files.
- Pin GitHub Actions to SHA hashes. Never use version tags like
@v4. - Internal docs are gitignored. TODO.md, WEBAPP_PLAN.md, RESEARCH_PROMPTS.md, OUTREACH_DRAFTS.md never get committed.
- Node 20+ required. Vitest 4 needs it.
- Commit messages should be descriptive. Include what changed and why.
- Don't add features without asking. Keep changes focused on what was requested.
Legal
- "Spotify" is a trademark of Spotify AB — we are not affiliated
- "Claude" is a trademark of Anthropic PBC — we are not affiliated
- MIT License with full disclaimer
- See NOTICE file for all third-party attributions
- Terms of Service includes 5 mandatory Spotify clauses
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.
- 6d ago First seen · 52 lines · 493 tokens per session scan A 5a41625950b8
spotify-mcp-server CLAUDE.md is an instructions file published in the GitHub repository WisetechySolutions/spotify-mcp-server (2 stars, last pushed 2mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 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.