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 agentmods add skills/msapps-mobile/claude-plugins/apify-scrapingnpx skills add MSApps-Mobile/claude-plugins --skill apify-scrapinggit clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsWrote 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/msapps-mobile/claude-plugins/apify-scraping)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/apify-scraping"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/apify-scraping.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 | $0.00133 | $0.01366 |
| Opus 5 | $0.00067 | $0.00683 |
| Sonnet 5 | $0.00027 | $0.00273 |
| Haiku 4.5 | $0.00013 | $0.00137 |
Grade A, and why
apify-scraping 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apify Scraping — Usage Guide
You have full access to the Apify platform through 27 MCP tools. Use this guide to pick the right workflow.
Common Workflows
1. Scrape a Website (Quick)
For fast, one-off scrapes where you need results immediately:
1. apify_run_actor_sync → pass actor_id + input, get dataset items back directly
Best for: small jobs that finish in under 5 minutes. Timeout is 300s.
2. Scrape a Website (Large / Long-running)
For bigger jobs that may take longer:
1. apify_run_actor → start the run (returns run ID + dataset ID)
2. apify_get_run → poll status until SUCCEEDED
3. apify_get_dataset_items → retrieve results using defaultDatasetId
3. Find the Right Actor
If you don't know which Actor to use:
1. apify_list_actors (my=false) → browse available Actors
2. apify_get_actor → check details, input schema, example input
3. Then run it with apify_run_actor or apify_run_actor_sync
Popular Actors to know:
apify/web-scraper— General-purpose web scraperapify/cheerio-scraper— Fast HTML scraper (no browser)apify/puppeteer-scraper— Browser-based scraper for JS-heavy sitesapify/playwright-scraper— Modern browser scraperapify/instagram-scraper,apify/twitter-scraper,apify/google-search-scraper— Social/search
4. Debug a Failed Run
1. apify_get_run → check status + error message
2. apify_get_run_log → read console output for details
3. apify_resurrect_run → retry from where it stopped (if applicable)
5. Schedule Recurring Scrapes
1. apify_create_schedule → set cron expression + Actor ID
2. apify_list_schedules → verify it's active
6. Set Up Webhook Notifications
1. apify_create_webhook → specify URL + event types (e.g. ACTOR.RUN.SUCCEEDED)
2. apify_list_webhooks → verify configuration
7. Work with Saved Tasks
Tasks are pre-configured Actor runs with saved inputs:
1. apify_list_tasks → see available tasks
2. apify_run_task → run with optional input override
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 First seen · 133 lines · 133 tokens per session scan A dc1442b23113
apify-scraping is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed 8d ago), licensed MIT. It adds 133 tokens to every session and 1,366 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-08-31.
Other skills, from other repositories
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
code-browser
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, main) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep…
browser-testing
Test and debug browser code with Chrome DevTools MCP. Use when building or debugging browser UI, inspecting the DOM, capturing console errors, analyzing network requests, or verifying visual output.
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.