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/TheWebScrapingClub/AI-Cursor-Scraping-AssistantWrote 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/thewebscrapingclub/ai-cursor-scraping-assistant/prerequisites)<a href="https://agentmods.dev/rules/thewebscrapingclub/ai-cursor-scraping-assistant/prerequisites"><img src="https://agentmods.dev/badge/rules/thewebscrapingclub/ai-cursor-scraping-assistant/prerequisites.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.1 | $0.00109 | $0.00109 |
| Opus 5 | $0.00055 | $0.00055 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
prerequisites 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prerequisites — 100% identical, 0 lines differ
What it actually says
description: This rule provides the action that should be taken before starting implementing a Scrapy spider. globs: **/*.py
Step by step prerequisites actions to perform
- Get with the pwd command the full path of the current project. Store in the context the current full path of the project. After you read it, please confirm in chat you did this step.
- Once you performed every prerequisite, write in chat that you performed all the prerequisite actions.
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.
- 8d ago First seen · 15 lines · 109 tokens per session scan A dcffd9b3285a
prerequisites is a cursor rule published in the GitHub repository TheWebScrapingClub/AI-Cursor-Scraping-Assistant (55 stars, last pushed 1y ago), licensed MIT. It adds 109 tokens to every session, about $0.0005 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-30.
Other cursor rules, from other repositories
scraper-models
Cursor rule "scraper-models" from Solihatun1/AI-Cursor-Scraping-Assistant, covering scraper types, e-commerce plp, e-commerce pdp, how to fill the scraper fields with values and how to create an e-commerce plp scraper.
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.
website-analysis
description: This rule provides a step by step guide to analyze a website and its code, in order to write a better Scrapy scraper. globs: /.py.
scrapy-step-by-step-process
description: This rule provides a step by step guide to follow for a successful Scrapy project. Read and implement the rules oncained in this file in first place. globs: /.py.
prerequisites
description: This rule provides the action that should be taken before starting implementing a Scrapy spider. globs: /.py.
utilities
// ✅ DO: Create focused, reusable utilities /.