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 agentmods add skills/jamiew/soundcloud-mcp/soundcloud-api-syncnpx skills add jamiew/soundcloud-mcp --skill soundcloud-api-syncgit clone --depth 1 https://github.com/jamiew/soundcloud-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/skills/jamiew/soundcloud-mcp/soundcloud-api-sync)<a href="https://agentmods.dev/skills/jamiew/soundcloud-mcp/soundcloud-api-sync"><img src="https://agentmods.dev/badge/skills/jamiew/soundcloud-mcp/soundcloud-api-sync.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 | $0.00072 | $0.01066 |
| Opus 5 | $0.00036 | $0.00533 |
| Sonnet 5 | $0.00014 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
soundcloud-api-sync 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SoundCloud API sync
SoundCloud ships API changes with no email list and no versioning. The GitHub release notes are the only real changelog, and endpoints have been removed from the public API without deprecation — they just start returning 405. This skill re-derives what is true from the official sources.
Run the audit first
node .claude/skills/soundcloud-api-sync/audit.mjs # latest 8 releases
node .claude/skills/soundcloud-api-sync/audit.mjs --since 2026-07-19
It fetches the live spec and prints three things:
- NOT IMPLEMENTED — spec operations no tool calls yet, method-aware
(
POST /trackscounts as missing even though weGET /tracks). - CALLED BUT NOT IN SPEC — the dangerous direction. Anything listed here is a candidate for the silent 405 treatment; verify it live before trusting it.
- RELEASES — dated release-note headlines.
Pass --since with the date in PLAN.md's "SoundCloud API synced through" line
to see only what is new, then update that line when done.
Authoritative sources, in order
| Source | URL | Use for |
|---|---|---|
| OpenAPI spec (YAML) | https://raw.githubusercontent.com/soundcloud/api/master/openapi/api.yaml |
The contract. Check before adding any endpoint. |
| Release notes | https://github.com/soundcloud/api/releases | The changelog. Nothing else lists changes. |
| Spec commit history | https://github.com/soundcloud/api/commits/master/openapi/api.yaml | Diffs between releases; chore: update OpenAPI spec commits land ahead of some notes. |
Agents.md |
https://github.com/soundcloud/api/blob/master/Agents.md | SoundCloud's own agent integration rules. |
| Cursor skills | .cursor/skills/ in soundcloud/api |
Their auth/discovery/integration guidance. Mirrors our CLAUDE.md rules. |
| LLM context | https://developers.soundcloud.com/docs/llm-context | Rate limits, upload limits, quotas in one page. |
| API guide | https://developers.soundcloud.com/docs/api/guide | Prose explanations. |
| Issue tracker | https://github.com/soundcloud/api/issues | Known bugs; releases cite issue numbers. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 80 lines · 72 tokens per session scan A e803560ff5b5
soundcloud-api-sync is a skill published in the GitHub repository jamiew/soundcloud-mcp (0 stars, last pushed 29d ago), licensed MIT. It adds 72 tokens to every session and 1,066 once invoked, about $0.0004 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…