Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/tmolavi/mcp-agent-skills-hub/apify-market-research)<a href="https://agentmods.dev/skills/tmolavi/mcp-agent-skills-hub/apify-market-research"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/apify-market-research/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/tmolavi/mcp-agent-skills-hub/apify-market-research"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/apify-market-research.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.00036 | $0.01184 |
| Opus 5.5 | $0.00014 | $0.00474 |
| Sonnet 5.5 | $0.00007 | $0.00237 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
apify-market-research 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 1mo 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.
This is a copy
98% identical to apify-market-research — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research
Conduct market research using Apify Actors to extract data from multiple platforms.
When to Use
- You need market sizing, regional demand, pricing, trend, or consumer behavior data.
- The task is to gather research inputs from maps, travel, Facebook, Instagram, or trend sources with Apify.
- You need structured market data plus a synthesized view of opportunities or risks.
Prerequisites
(No need to check it upfront)
.envfile withAPIFY_TOKEN- Node.js 20.6+ (for native
--env-filesupport) mcpcCLI tool:npm install -g @apify/mcpc
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify market research type (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analysis script
- [ ] Step 5: Summarize findings
Step 1: Identify Market Research Type
Select the appropriate Actor based on research needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Market density | compass/crawler-google-places |
Location analysis |
| Geospatial analysis | compass/google-maps-extractor |
Business mapping |
| Regional interest | apify/google-trends-scraper |
Trend data |
| Pricing and demand | apify/facebook-marketplace-scraper |
Market pricing |
| Event market | apify/facebook-events-scraper |
Event analysis |
| Consumer needs | apify/facebook-groups-scraper |
Group research |
| Market landscape | apify/facebook-pages-scraper |
Business pages |
| Business density | apify/facebook-page-contact-information |
Contact data |
| Cultural insights | apify/facebook-photos-scraper |
Visual research |
| Niche targeting | apify/instagram-hashtag-scraper |
Hashtag research |
| Hashtag stats | apify/instagram-hashtag-stats |
Market sizing |
| Market activity | apify/instagram-reel-scraper |
Activity analysis |
| Market intelligence | apify/instagram-scraper |
Full data |
| Product launch research | apify/instagram-api-scraper |
API access |
| Hospitality market | voyager/booking-scraper |
Hotel data |
| Tourism insights | maxcopell/tripadvisor-reviews |
Review analysis |
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.
- 1mo ago First seen · 131 lines · 36 tokens per session scan A 07139b22d05d
apify-market-research is a skill published in the GitHub repository tmolavi/mcp-agent-skills-hub (8 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,184 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to apify-market-research, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
ai-output-validation
Validates, parses, and sanitizes AI-generated outputs before they reach end users or downstream systems. Structured output enforcement, schema validation, and fallback handling.
integration-testing
Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.
shipping-and-launch
A production-release checklist and planning guide for putting software in front of real users. It covers testing, security, monitoring, staged rollout, and rollback, which means returning to the previous working version.
taming-copilot
Your mission is to be a precise, surgical assistant that respects existing code, follows user commands absolutely, and avoids any unsolicited changes.
pod-troubleshooting
Systematic diagnosis of Kubernetes pod failures — CrashLoopBackOff, OOMKilled, Pending, ImagePullBackOff, and service connectivity issues. Use when the user encounters pods not starting, container restart loops, scheduling failures, or service unreachability in a K8s cluster.