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 humaisali/Awesome-AI-Skills --skill apify-actor-developmentgit clone --depth 1 https://github.com/humaisali/Awesome-AI-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/humaisali/awesome-ai-skills/apify-actor-development)<a href="https://agentmods.dev/skills/humaisali/awesome-ai-skills/apify-actor-development"><img src="https://agentmods.dev/badge/skills/humaisali/awesome-ai-skills/apify-actor-development/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/humaisali/awesome-ai-skills/apify-actor-development"><img src="https://agentmods.dev/badge/skills/humaisali/awesome-ai-skills/apify-actor-development.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.00071 | $0.02884 |
| Opus 5 | $0.00036 | $0.01442 |
| Sonnet 5 | $0.00014 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00288 |
Grade A, and why
apify-actor-development 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 9d 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
94% identical to apify-actor-development — 5 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apify Actor Development
Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
When to Use
- You need to create, modify, or debug an Apify Actor project.
- The task involves choosing an Apify template, wiring actor inputs/outputs, or implementing actor runtime logic.
- You need safe setup guidance for
apifyCLI authentication, project bootstrap, or deployment workflow.
What are Apify Actors?
Actors are serverless programs inspired by the UNIX philosophy - programs that do one thing well and can be easily combined to build complex systems. They're packaged as Docker images and run in isolated containers in the cloud.
Core Concepts:
- Accept well-defined JSON input
- Perform isolated tasks (web scraping, automation, data processing)
- Produce structured JSON output to datasets and/or store data in key-value stores
- Can run from seconds to hours or even indefinitely
- Persist state and can be restarted
Prerequisites & Setup (MANDATORY)
Before creating or modifying actors, verify that apify CLI is installed apify --help.
If it is not installed, use one of these methods (listed in order of preference):
# Preferred: install via a package manager (provides integrity checks)
npm install -g apify-cli
# Or (Mac): brew install apify-cli
Security note: Do NOT install the CLI by piping remote scripts directly into a shell. Always use a package manager.
When the apify CLI is installed, check that it is logged in with:
apify info # Should return your username
If it is not logged in, check if the APIFY_TOKEN environment variable is defined (if not, ask the user to generate one on https://console.apify.com/settings/integrations and then define APIFY_TOKEN with it).
Then authenticate using one of these methods:
What ships with it
7 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.
- 9d ago First seen · 230 lines · 71 tokens per session scan A d39693ca393c
apify-actor-development is a skill published in the GitHub repository humaisali/Awesome-AI-Skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 2,884 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to apify-actor-development, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
using-webctl
Browser automation via webctl CLI in Claude.ai containers with authenticated proxy support. Use when users mention webctl, browser automation, Playwright browsing, web scraping, or headless Chrome in container environments.
openclaw-browser-auto
A setup guide for connecting OpenClaw, an AI-agent platform, to a remote Chrome browser through CDP, a browser control interface. It covers Docker-hosted browsers and Browserless.io, a hosted browser service.
vercel-sandbox
Run chrome-use + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across…
openclaw-browser
When OpenClaw runs in Docker, host-local services are not available at localhost from inside the browser container context.
openwork-docker-chrome-mcp
Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: "dev-up.sh" "docker dev stack" "verify in chrome mcp" "test the real flow".
docker-and-scraper-reliability
Use when running Playwright or Selenium scrapers in Docker, handling Cloudflare challenges, managing browser session persistence across restarts, or implementing health checks for headless Chrome.