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.
git clone --depth 1 https://github.com/apify/apify-cursor-pluginWrote 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/rules/apify/apify-cursor-plugin/apify-routing)<a href="https://agentmods.dev/rules/apify/apify-cursor-plugin/apify-routing"><img src="https://agentmods.dev/badge/rules/apify/apify-cursor-plugin/apify-routing/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/rules/apify/apify-cursor-plugin/apify-routing"><img src="https://agentmods.dev/badge/rules/apify/apify-cursor-plugin/apify-routing.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.00080 | $0.00936 |
| Opus 5.5 | $0.00032 | $0.00374 |
| Sonnet 5.5 | $0.00016 | $0.00187 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
apify-routing 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apify Routing
Cursor exposes Apify skills (apify-actor-development, apify-actorization, apify-generate-output-schema, apify-sdk-integration, apify-ultimate-scraper) directly in the slash menu. They are internal capabilities owned by the apify subagent and must not be invoked on their own.
Required Behavior
When the user's request involves Apify — Actors, web scraping, browser automation, the Apify Store, the Apify SDK, the Apify CLI, the apify or apify-client npm packages, or anything at apify.com / console.apify.com — invoke the apify subagent first. Let it consult its routing matrix and dispatch to the correct skill or MCP tool.
Do not:
- Call any
apify-*skill directly from the slash menu without going through theapifysubagent. - Guess between
apify-actor-developmentvsapify-actorizationvsapify-sdk-integrationyourself — the subagent owns that decision (theapifySDK package and theapify-clientpackage are easy to confuse and picking wrong breaks the user's project). - Skip the subagent for "quick" Apify questions. Even direct Apify MCP tool calls are routed through the subagent.
If the user types a slash command for an Apify skill explicitly, still hand off to the apify subagent so the routing matrix and authentication guidance are applied.
Why this rule exists
Apify exposes three very different products through its plugin: (1) using existing Actors via MCP, (2) building and deploying custom Actors with the SDK + CLI, and (3) calling Actors from an existing application via apify-client. Each path requires a different skill, a different authentication flow, and a different npm package. The apify subagent is the only place where the routing matrix and the package-naming trap are documented, so every Apify request must pass through it.
Apify CLI instructions:
Rule: pass --user-agent apify-cursor-plugin/apify-routing only on actor start and actor run commands (apify actors start, apify actors call). Do not add it to login, info, or other CLI commands.
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 Changed · +4 lines 3ede06a11622
- 2mo ago First seen · 50 lines · 80 tokens per session scan A f37ac965e6df
apify-routing is a cursor rule published in the GitHub repository apify/apify-cursor-plugin (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 80 tokens to every session and 936 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-31.
Other cursor rules, from other repositories
webrtc
Choose ordered/reliable vs unreliable per use case deliberately. Set maxRetransmits or maxPacketLifeTime (never both) for partial reliability; leave both unset only when full reliability is actually required. State sync wants reliable; real-time telemetry wants unreliable. (W3C WebRTC — RTCDataChannel /…
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
chrome-extension-manifest-rules
Specific rules related to the Chrome extension manifest file, ensuring proper structure and content.
vla-registry
Multi-model GUI/VL registry — browser wllama grounding (ShowUI-2B is default + E2E gate).
safari
This file, safari.mdc, serves as a repository for detailed working notes, observations, and learnings acquired during the process of automating Safari interactions, particularly for the MCP Inspector UI. It's intended to capture the nuances of trial-and-error, debugging steps, and insights into what worked, what…
scrapy
Cursor rule "scrapy" from Solihatun1/AI-Cursor-Scraping-Assistant, covering scrapy best practices, 1. code organization and structure, 1.1. directory structure, 1.2. file naming conventions and 1.3. module organization.