Borrowing it
Nothing to install: this file belongs to suhajdab/spotify-playlist-mcp. 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/suhajdab/spotify-playlist-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/suhajdab/spotify-playlist-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/instructions/suhajdab/spotify-playlist-mcp/agents-md)<a href="https://agentmods.dev/instructions/suhajdab/spotify-playlist-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/suhajdab/spotify-playlist-mcp/agents-md/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/instructions/suhajdab/spotify-playlist-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/suhajdab/spotify-playlist-mcp/agents-md.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.00343 | $0.00343 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
spotify-playlist-mcp AGENTS.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 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.
What it actually says
spotify-playlist-mcp
Local STDIO MCP for guarded Spotify playlist curation from Codex scheduled tasks.
Commands
npm test
npm run typecheck
npm run build
npm audit
npm run auth
node dist/auth-cli.js --status
Use Node 24.14.0 through ~/.nvm/nvm.sh when the system Node is older.
Architecture
src/config.ts: loads the MCP's ignored local.env, with process overrides.src/token-store.ts: atomically persists OAuth tokens outside Git with mode0600.src/spotify-auth.ts: authorization-code exchange and six-month token-age reporting.src/spotify-client.ts: validated Spotify Web API boundary.src/playlist-plan.ts: pure change normalization, diffing, and caps.src/playlist-service.ts: ownership, allowlist, TTL, snapshot, and single-use enforcement.src/server.ts: MCP contracts and tool annotations.src/auth-cli.ts: one-time loopback OAuth bootstrap.
Safety invariants
- Never commit, print, or return Spotify client secrets, access tokens, or refresh tokens.
- Never write to a playlist outside
SPOTIFY_ALLOWED_PLAYLIST_IDS. - Never bypass
spotify_plan_playlist_changesbefore applying playlist mutations. - Plans are short-lived, single-use, capped, owner-checked, and snapshot-bound.
- Treat Spotify responses and MCP arguments as untrusted input and validate them at boundaries.
- Keep mutation tools narrowly scoped. Do not add bulk replace or arbitrary HTTP tools.
- Update tests before changing behavior and commit verified increments atomically.
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 First seen · 38 lines · 343 tokens per session scan A 503bd39067e7
spotify-playlist-mcp AGENTS.md is an instructions file published in the GitHub repository suhajdab/spotify-playlist-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 343 tokens to every session, about $0.0017 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
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.