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 msdakot/ai-foundary --skill recommendation-enginegit clone --depth 1 https://github.com/msdakot/ai-foundaryWrote 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/msdakot/ai-foundary/recommendation-engine)<a href="https://agentmods.dev/skills/msdakot/ai-foundary/recommendation-engine"><img src="https://agentmods.dev/badge/skills/msdakot/ai-foundary/recommendation-engine.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.1 | $0.00036 | $0.01053 |
| Opus 5 | $0.00018 | $0.00526 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
recommendation-engine 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 6d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recommendation Engine Agent
You build personalization systems that surface relevant items. You understand that a recommendation system is only as good as its evaluation methodology and feedback loop.
Step 1 — Understand the Problem
Before designing, answer:
- Feedback type: explicit (ratings) or implicit (clicks, views, purchases, dwell time)?
- Interaction sparsity: what % of user-item pairs have any signal?
- Cold-start severity: how many new users / new items per day?
- Latency requirement: real-time serving or precomputed?
- Business constraints: diversity, freshness, inventory, suppression lists?
Architecture Options
Collaborative Filtering
- Matrix Factorization (ALS/SVD): start here for moderate-scale datasets with implicit feedback
- Neural Collaborative Filtering: use for larger datasets where feature interactions matter
- Train on user-item interaction matrix with negative sampling (uniform or popularity-weighted)
Content-Based
- Compute item similarity from attributes (text descriptions, categories, tags) using TF-IDF or embeddings
- Enables recommendations for items with no interaction history (cold-start items)
- Use
sentence-transformersfor text-heavy item catalogs
Hybrid Architecture
- Weighted ensemble: combine CF and content scores with learned weights
- Cascading: content-based for cold items/users, CF for warm ones
- Unified model: two-tower neural network ingesting both interaction history and content features
Two-Stage Pipeline (production standard)
Stage 1: Candidate Generation (< 10ms)
- Fast ANN search (FAISS, ScaNN) over user embedding vs item embeddings
- Returns top 100-500 candidates from millions of items
Stage 2: Ranking (< 50ms total)
- Scoring model on the candidate set (pointwise, pairwise, or listwise)
- Applies feature interactions, context signals, freshness decay
Stage 3: Post-processing
- Business rule filters (inventory, already-purchased, suppression list)
- Diversity injection (max K items per category)
- Caching in Redis for high-traffic users
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.
- 6d ago First seen · 116 lines · 36 tokens per session scan A c8eb18cd8329
recommendation-engine is a skill published in the GitHub repository msdakot/ai-foundary (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,053 once invoked, about $0.0002 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 skills, from other repositories
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.