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/apify/awesome-skills/_templatenpx skills add apify/awesome-skills --skill _templategit 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/_template)<a href="https://agentmods.dev/skills/apify/awesome-skills/_template"><img src="https://agentmods.dev/badge/skills/apify/awesome-skills/_template.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.00000 | $0.00895 |
| Opus 5 | $0.00000 | $0.00447 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
_template 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REPLACE: Skill Title
REPLACE: One-line summary of what this skill helps the agent accomplish.
Example prompts
Prompts this skill handles:
- "REPLACE: a real prompt a user would type"
- "REPLACE: a second one, phrased differently"
Out of scope (the boundary):
- "REPLACE: a nearby request this skill deliberately does not handle — and where to send it instead"
Prerequisites
- Apify account (sign up)
- Authentication via one of:
apify login(OAuth, if using the Apify CLI)APIFY_TOKENenvironment variable- Token from Apify Console → Settings → Integrations
Workflow
- REPLACE: Understand the user's goal, pick the right Actor(s).
- REPLACE: Fetch the Actor's input schema, build a valid input.
- REPLACE: Run the Actor, confirm with user if estimated cost is significant.
- REPLACE: Deliver results (count, format, link to dataset/console).
For a worked 4-step workflow, see apify/agent-skills ultimate-scraper.
Actor routing
| User need | Actor ID | Tier | Best for |
|---|---|---|---|
| REPLACE | apify/REPLACE-actor |
apify | REPLACE |
| REPLACE | community/REPLACE-actor |
community | REPLACE |
Tier = apify (Apify-maintained, prefer) or community (third-party).
Calling Actors — choose your interface
Skills in this repo can call Actors via any of these interfaces. Pick the one that fits your runtime; cross-tool compatibility is your responsibility.
Option A: Apify CLI (recommended for portability)
Works in any shell-capable agent. Three flags on every call:
apify actors call "ACTOR_ID" -i 'JSON_INPUT' \
--json \
--user-agent apify-awesome-skills/REPLACE-skill-name \
2>/dev/null
| Flag | Why |
|---|---|
--json |
Stable machine-readable output |
--user-agent |
Apify telemetry attribution |
2>/dev/null |
Suppress progress messages that break JSON |
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.
- 4d ago First seen · 103 lines · 0 tokens per session scan A 226498e5292d
_template is a skill published in the GitHub repository apify/awesome-skills (248 stars, last pushed 21d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 895 tokens. 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
apify-generate-output-schema
Generate output schemas (datasetschema.json, outputschema.json, keyvaluestoreschema.json) for an Apify Actor by analyzing its source code. Use when creating or updating Actor output schemas.
apify-sdk-integration
Integrate Apify into an existing JavaScript/TypeScript or Python application using the apify-client package. Use when adding web scraping, automation, or data extraction capabilities to an existing app via the Apify API.
apify-ultimate-scraper
Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, LinkedIn, X/Twitter, Google Maps, Google Search, Google Trends, Reddit, Airbnb, Yelp, and 15+ more platforms. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research…
apify-actor-development
Develop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automation, and data processing. Use when creating new Actors, modifying existing ones, or troubleshooting Actor code.
apify-actorization
Convert existing projects into Apify Actors - serverless cloud programs. Actorize JavaScript/TypeScript (SDK with Actor.init/exit), Python (async context manager), or any language (CLI wrapper). Use when migrating code to Apify, wrapping CLI tools as Actors, or adding Actor SDK to existing projects.
stack-merge
Bulk-merge a Graphite stack into main via admin-bypass fast-forward push. Replaces the Graphite merge queue for rivet-dev/rivet. Invoke when the user says "merge the stack at ", "ship everything through ", "bulk-merge up to ", "fast-forward main to ", or any request to land multiple stacked PRs at once in one shot.…