Borrowing it
Nothing to install: this file belongs to jaminben/secure-applemusic-mcp-for-osx. 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/jaminben/secure-applemusic-mcp-for-osx/main/CLAUDE.mdgit clone --depth 1 https://github.com/jaminben/secure-applemusic-mcp-for-osxWrote 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/jaminben/secure-applemusic-mcp-for-osx/claude-md)<a href="https://agentmods.dev/instructions/jaminben/secure-applemusic-mcp-for-osx/claude-md"><img src="https://agentmods.dev/badge/instructions/jaminben/secure-applemusic-mcp-for-osx/claude-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/jaminben/secure-applemusic-mcp-for-osx/claude-md"><img src="https://agentmods.dev/badge/instructions/jaminben/secure-applemusic-mcp-for-osx/claude-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.01628 | $0.01628 |
| Opus 5 | $0.00814 | $0.00814 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
secure-applemusic-mcp-for-osx CLAUDE.md scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Do not read these numbers out of an ad-hoc `gh api` or `curl` call and let them How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repo
A hardened, macOS-only fork of epheterson/applemusic-mcp, shipped as a
notarized .app and a PyPI wheel. The fork's reason to exist is a smaller
capability surface, so anything that widens it is a regression, not a feature.
Tracking downloads and traffic
Whenever you pull download, traffic, or listing stats, record them:
make stats # collect and append to stats/downloads.csv
make stats-show # print the trend
Do not read these numbers out of an ad-hoc gh api or curl call and let them
evaporate into the transcript. Run the collector, then quote from what it wrote.
If the user asks for a number the collector does not yet gather, add it to
scripts/collect_stats.py rather than fetching it by hand.
Why: GitHub's traffic API keeps only 14 days. Views and clones older than a fortnight are unrecoverable — no export, no archive. Per-asset release counts never expire but are only ever exposed as a running total, so "how did 0.3.1 do in its first week" is unanswerable unless something wrote it down at the time.
stats/downloads.csv is long format — date,source,metric,value — because the
metric set grows with every release. Re-running replaces only the (date, source) pairs it actually collected, so a later run that hits a rate limit
cannot delete what an earlier successful run recorded, and hand-added rows
survive.
Two rows did not come from the collector and are worth knowing about:
- 2026-08-30 was reconstructed from a session transcript after the fact,
dated by bracketing commits
df90a00(08-29 23:14) andff2efe8(08-30 22:31). Its per-asset counts sum to its recorded total, which is the check that says the reconstruction is internally consistent. source=pepyis a page scrape, not an API read. pepy counts mirror traffic and pypistats does not, which is why they disagree by roughly 5x. They are kept as separate sources so the two are never averaged together.
The one rule that matters
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.
- 5d ago First seen · 139 lines · 1,628 tokens per session scan A de6894b96a21
secure-applemusic-mcp-for-osx CLAUDE.md is an instructions file published in the GitHub repository jaminben/secure-applemusic-mcp-for-osx (0 stars, last pushed 4d ago), licensed MIT. It adds 1,628 tokens to every session, about $0.0081 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It comes from a forked repository.
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.