Borrowing it
Nothing to install: this file belongs to umsachde/re-com. 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/umsachde/re-com/main/.claude/skills/recom-index-setup/SKILL.mdgit clone --depth 1 https://github.com/umsachde/re-comWrote 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/umsachde/re-com/recom-index-setup)<a href="https://agentmods.dev/skills/umsachde/re-com/recom-index-setup"><img src="https://agentmods.dev/badge/skills/umsachde/re-com/recom-index-setup/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/skills/umsachde/re-com/recom-index-setup"><img src="https://agentmods.dev/badge/skills/umsachde/re-com/recom-index-setup.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.00073 | $0.01914 |
| Opus 5.5 | $0.00029 | $0.00766 |
| Sonnet 5 | $0.00015 | $0.00383 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
recom-index-setup 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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
These are offline maintenance scripts (README.md "Setup", PLAN.md §7.4), run
by hand from the command line. They are not part of the live tool-call path.
Full first-time setup takes roughly 45 minutes; most of that is the atlas crawl
in step 1.
Use .venv/bin/python, not python — the deps are in the venv. (Its console
scripts such as .venv/bin/pytest may carry a stale shebang from an earlier
project name; .venv/bin/python -m pytest works regardless.)
Credentials differ per script — check before running
v6 moved some of these onto the provider.Provider seam and left others on
ytmusicapi deliberately. The seam scripts reach the account through the
ytmusic-mcp subprocess, so they need it pointed out to them in the
environment, and crash on startup without it:
RuntimeError: ytmusic-mcp is not configured. Set RECOM_YTMUSIC_MCP_COMMAND ...
| script | how it reaches the account |
|---|---|
build_atlas.py |
ytmusicapi directly, RECOM_AUTH_PATH (default headers_auth.json) |
build_genres.py |
ytmusicapi directly, RECOM_AUTH_PATH |
build_tempo.py |
neither — store + Deezer's public API only |
build_graph_atlas.py |
neither — Deezer + the store (propagate is store-side) |
label_library.py |
Provider seam → needs the env below |
snapshot_history.py |
Provider seam → needs the env below |
quality_check.py |
Provider seam → needs the env below |
The values are whatever the re-com MCP server is already configured with in
~/.claude.json (mcpServers.re-com.env) — read them from there rather than
guessing:
export RECOM_YTMUSIC_MCP_COMMAND=/path/to/ytmusic-mcp/.venv/bin/python
export RECOM_YTMUSIC_MCP_ARGS=/path/to/ytmusic-mcp/server.py
export YTMUSIC_AUTH_PATH=/path/to/ytmusic-mcp/headers_auth.json
For Spotify it is the RECOM_SPOTIFY_MCP_* pair plus RECOM_PROVIDER=spotify,
from mcpServers.re-com-spotify.env.
Order matters — run in this sequence
# (prefix the Provider-seam scripts with the env above)
# 1. Crawl YouTube's editorial mood atlas (~35 min, resumable, safe to interrupt)
.venv/bin/python scripts/build_atlas.py
# 2. Label your library from that atlas + artist propagation (needs only YouTube Music creds)
.venv/bin/python scripts/label_library.py
# 3. Genre/language labels, for the language filter (~10-15 min)
.venv/bin/python scripts/build_genres.py
# 4. Tempo/BPM, from Deezer's public API (~0.4s per song)
.venv/bin/python scripts/build_tempo.py
# 5. Optional: cross-backend mood corpus via Deezer playlist search (works on any backend)
.venv/bin/python scripts/build_graph_atlas.py
# 6. Optional: have Claude read lyrics to cover what the atlas missed (needs an API key)
pip install -e ".[llm]"
.venv/bin/python scripts/label_library.py --claude
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.
- 2d ago Changed · +76 lines 22331dacd3de
- 10d ago First seen · 83 lines · 73 tokens per session scan A 77f5ab65e816
recom-index-setup is a skill published in the GitHub repository umsachde/re-com (0 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,914 once invoked, about $0.0003 per session on Opus 5.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-14.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…