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 apify/awesome-skills --skill apify-product-data-setupgit clone --depth 1 https://github.com/apify/awesome-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/apify/awesome-skills/apify-product-data-setup)<a href="https://agentmods.dev/skills/apify/awesome-skills/apify-product-data-setup"><img src="https://agentmods.dev/badge/skills/apify/awesome-skills/apify-product-data-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/apify/awesome-skills/apify-product-data-setup"><img src="https://agentmods.dev/badge/skills/apify/awesome-skills/apify-product-data-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.00132 | $0.01836 |
| Opus 5 | $0.00066 | $0.00918 |
| Sonnet 5 | $0.00026 | $0.00367 |
| Haiku 4.5 | $0.00013 | $0.00184 |
Grade A, and why
apify-product-data-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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- apify-product-data-setup — 88% identical, 15 lines differ
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apify product data setup
Connect an agent to current product data: price, stock, brand, rating, and image URLs from retailer pages. Nothing to host.
Written by a product marketing manager at Apify. It routes to E-commerce Scraping Tool, a paid first-party Apify Actor, so treat the framing accordingly. No affiliate links.
Choose the path first
The two paths are not interchangeable and the cost model is what separates them.
| Runtime call | Scheduled refresh | |
|---|---|---|
| When | The answer must be true right now, few products | A catalog answered from repeatedly |
| Transport | MCP | REST API |
| Cost shape | A start event per call, plus per product | One start event per batch |
| Latency the user feels | Seconds to tens of seconds | None, the index is already warm |
Most production setups want both: a scheduled refresh for breadth, plus a runtime call to verify a single item when the user asks for a price they will act on.
A cron job gains nothing from MCP, so the scheduled path uses the REST API. Say so when explaining the design, because the mismatch looks like an oversight otherwise.
Connect over MCP
The server is https://mcp.apify.com. Narrow it to this Actor with ?tools=apify/e-commerce-scraping-tool, which makes tool selection more reliable when product data is the only job. Drop the parameter to let the agent search all of Apify Store at runtime.
Config blocks per client are in references/clients.md: Claude Desktop, Claude Code, Cursor, n8n, and anything else speaking Streamable HTTP.
Authentication: OAuth on first use for interactive clients, a bearer token from Apify Console for unattended ones.
Encode the fetch flow
Fetching products starts with the Actor call, may require several status polls, and finishes with one dataset read. This is the single most important thing to get into the agent's instructions:
apify--e-commerce-scraping-toolreturns run metadata and adatasetId. No products.- If
statusis not terminal, pollget-actor-runwith the validatedrunIduntil it succeeds or a caller-defined deadline expires. TreatFAILED,ABORTED, andTIMED-OUTas failures. The Actor tool returns when its own wait window elapses rather than when the run finishes, soRUNNINGis a normal answer and the dataset is empty at that moment. get-dataset-itemsreturns the products. Passfieldsin dot notation: the unprojected record measured about 88 KB across 142 fields, and projecting keeps that out of the context window.
What ships with it
2 files 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.
- today First seen · 109 lines · 132 tokens per session scan A f2787e44e656
apify-product-data-setup is a skill published in the GitHub repository apify/awesome-skills (251 stars, last pushed today), licensed Apache-2.0. It adds 132 tokens to every session and 1,836 once invoked, about $0.0007 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-10.
Other skills, from other repositories
apify-product-data-setup
Wire an AI agent to live e-commerce product data using Apify's E-commerce Scraping Tool over MCP, either as runtime tool calls or as a scheduled refresh into a vector store. Trigger on "give my agent live product data", "my agent quotes stale prices", "connect Apify MCP to Claude or Cursor or n8n", "add product data…
iterative-retrieval
Pattern for progressively refining context retrieval to solve the subagent context problem.
knowledge-graph-creation
Build structured knowledge graphs from unstructured text by extracting entities, mapping relationships, generating graph triples, and visualizing the result. Use when the user requests knowledge graph creation or provides relevant inputs for this workflow.
context-retrieval
Retrieve relevant information from a knowledge base using semantic, keyword, or hybrid search to ground a query. Use when the task starts with a corpus or index that must be searched; use context-ranking when candidate chunks already exist and only need ordering.
context-ranking
Rank an existing set of context chunks by relevance, diversity, freshness, and utility. Use when retrieval has already produced candidates that must be scored or reranked; use context-retrieval when the source corpus still needs to be searched.
langchain
LangChain skill for building LLM orchestration, agents, RAG pipelines, tools, memory, callbacks, and deployment.