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 skills add PracticalSwan/agent-skills --skill recommender-evaluationgit clone --depth 1 https://github.com/PracticalSwan/agent-skillsWrote 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/practicalswan/agent-skills/recommender-evaluation)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/recommender-evaluation"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/recommender-evaluation/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/practicalswan/agent-skills/recommender-evaluation"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/recommender-evaluation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 138 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00107 | $0.02623 |
| Opus 5 | $0.00053 | $0.01311 |
| Sonnet 5 | $0.00021 | $0.00525 |
| Haiku 4.5 | $0.00011 | $0.00262 |
Grade A, and why
recommender-evaluation 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 4d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recommender Evaluation
This skill defines how the Vinyl Record Store recommender is measured. It exists because recommender quality is judged on ranking and catalog health, not MSE/RMSE — applying regression metrics to a top-k recommender is a classic, grade-costing mistake.
When to use
- You are about to compute or report a number about recommendation quality.
- You are designing the train/test split or deciding what counts as "relevant."
- You are comparing two algorithms and need a fair, side-by-side table.
- You are writing the Evaluation section of a CSX4207 report or slide.
Step 0 — Define "relevant" before touching metrics
Pin this down explicitly and write it in the report:
- Explicit ratings: "relevant" usually = rating ≥ threshold (e.g., ≥ 4 of 5).
- Implicit feedback: "relevant" = user interacted (play/purchase) in the held-out period; for ranking metrics, consider only items the user hasn't already consumed from training.
Ambiguity here invalidates every downstream number.
Step 1 — Split without leakage
- Leave-one-out per user (small data): hold out each user's most recent (or a random one) interaction for test; train on the rest. Standard for HitRate@k / NDCG@k on sparse academic datasets.
- Temporal split (preferred when timestamps exist): train on interactions before time T, test on after T. Closest to production reality.
- Never random row-shuffle split that lets a user appear in both train and test with overlapping context — it leaks and inflates every metric.
- For top-k ranking eval, sample negatives (items the user didn't interact with) to rank against the held-out positive, or rank against the full catalog (more honest, more expensive). State which.
Step 2 — Ranking-accuracy metrics (report at least NDCG@k + MAP@k)
For a user u, let the top-k recommendation list be R_k(u) and the set of relevant items be Rel(u).
- Precision@k =
|Rel(u) ∩ R_k(u)| / k - Recall@k =
|Rel(u) ∩ R_k(u)| / |Rel(u)| - HitRate@k =
1if|Rel(u) ∩ R_k(u)| ≥ 1else0(mean over users) - MRR (Mean Reciprocal Rank) = mean over users of
1 / rank_of_first_relevant - AP@k (Average Precision) =
(1 / min(k, |Rel(u)|)) · Σ_{i=1..k} Precision@i · rel(i), whererel(i)=1if item at rank i is relevant. MAP@k = mean of AP@k over users. - DCG@k =
Σ_{i=1..k} rel_i / log2(i + 1)(use2^rel − 1if graded relevance). IDCG@k = DCG of the ideal ordering. NDCG@k =DCG@k / IDCG@k∈ [0,1].
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.
- 4d ago Changed 013427dc0183
- 6d ago Changed 472f44a19967
- 8d ago First seen · 185 lines · 107 tokens per session scan A e50f9dd941b5
recommender-evaluation is a skill published in the GitHub repository PracticalSwan/agent-skills (14 stars, last pushed 4d ago), licensed MIT. It adds 107 tokens to every session and 2,623 once invoked, about $0.0005 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-03.
Other skills, from other repositories
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
product-description-generator
E-commerce product description generator for any platform. Generates optimized titles, bullet points, descriptions, and backend keywords using competitor research + keyword scoring + FABE copywriting. Two modes: (A) Create — generate listing from product specs with optional competitor analysis, (B) Optimize — improve…