Apify MCP Server connects AI agents to Apify's collection of web scrapers, crawlers, and automation tools through the Model Context Protocol, allowing them to extract data from websites, search engines, social media, maps, and online stores. It is for users who want agents to collect web data through compatible clients such as Claude Code, Claude.ai, Cursor, or VS Code. The catalogue entries configure or extend agent use of this MCP server.
Borrowing it
Nothing to install: this file belongs to apify/apify-mcp-server. 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/apify/apify-mcp-server/master/.claude/skills/dig/SKILL.mdgit clone --depth 1 https://github.com/apify/apify-mcp-serverWrote 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/apify-mcp-server/dig)<a href="https://agentmods.dev/skills/apify/apify-mcp-server/dig"><img src="https://agentmods.dev/badge/skills/apify/apify-mcp-server/dig/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/apify-mcp-server/dig"><img src="https://agentmods.dev/badge/skills/apify/apify-mcp-server/dig.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.02060 |
| Opus 5.5 | $0.00026 | $0.00824 |
| Sonnet 5.5 | $0.00013 | $0.00412 |
| Haiku 4.5 | $0.00006 | $0.00206 |
Grade A, and why
dig 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 2mo 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.
Dig
Flexible skill for exploring, planning, and speccing work on the Apify MCP server. Do NOT edit source files — this skill is for understanding and planning only.
Step 0: Parse arguments and determine intent
$ARGUMENTS contains the user's request and optional repo path overrides.
Flags (optional):
| Flag | Default | Purpose |
|---|---|---|
--sdk |
../typescript-sdk |
MCP SDK source repo path |
--ext-apps |
../ext-apps |
MCP Apps SDK source repo path |
--internal |
../apify-mcp-server-internal |
Internal server repo path |
Everything not matching a flag is the user's request.
Resolution order for source repos: flag path → default sibling path → node_modules/ (compiled types only) → GitHub URL (last resort). Always verify the path exists before using it.
Determine the intent
Infer the intent from the user's natural language. There are three modes:
| Intent | What you do | Examples |
|---|---|---|
| Explore | Read code, explain findings, answer questions | "how does tool naming work", "look at the widget code", "why is this broken", "what would break if we change X" |
| Plan | Enter plan mode, design the approach, assess impact | "plan implementing resource links", "figure out how to refactor metadata", "design the simplification" |
| Spec | Plan + create GitHub issues | "write an issue for X", "create a spec for Y", "spec out resource links" |
Rules:
- Default to Explore. When in doubt, do less — the user can always ask for more.
- Only enter plan mode for Plan and Spec.
- Only create GitHub issues for Spec.
Step 1: Explore
Read the relevant source files and explain your findings. This is the baseline for all intents.
What to do:
- Read the relevant source files in this repo
- Check similar existing features as reference
- Only check the internal repo, MCP SDK/spec, or MCP Apps SDK/spec if the user's question touches those areas
- If you spot a related open issue, mention it casually — but don't go searching for issues unless it's relevant
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.
- 2mo ago First seen · 159 lines · 64 tokens per session scan A 7a5baa55a043
dig is a skill published in the GitHub repository apify/apify-mcp-server (13,682 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,060 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-08-30.
Other skills, from other repositories
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
data-cleanup
Check your CRM board's health and clean up messy data — run a scored health check (missing fields, stalled deals, abandoned columns, automation gaps) as a report, or fix data in bulk (phone formats, missing emails, country codes, unowned deals, stale dates). Use when someone says "clean my CRM", "fix my data"…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
workspace-builder
Build a CRM workspace from scratch — describe your business and get boards, columns, and pipeline stages created in monday. Use when someone says "set up my CRM", "build me a CRM", "create CRM boards for me", "I need a new sales pipeline", "help me get started in monday", "I don't know how to set up my pipeline", or…
forecast
Build a forecast dashboard in monday — committed, best-case, and pipeline views by close month, rendered as real dashboard widgets. Use when someone says "build me a forecast", "show me Q2 pipeline", "Salesforce-style forecast", "forecast dashboard", "commit vs best-case", "what's our number this quarter", "how are we…
run-sequence
Manage CRM sequences end-to-end — list, create, enroll contacts, activate/deactivate, duplicate, and track performance. Use when someone says "what sequences do I have", "create a welcome sequence", "enroll this contact in a sequence", "add these leads to my nurture sequence", "deactivate the cold outreach sequence"…