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 rules/solihatun1/ai-cursor-scraping-assistant/website-analysisgit clone --depth 1 https://github.com/Solihatun1/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/solihatun1/ai-cursor-scraping-assistant/website-analysis)<a href="https://agentmods.dev/rules/solihatun1/ai-cursor-scraping-assistant/website-analysis"><img src="https://agentmods.dev/badge/rules/solihatun1/ai-cursor-scraping-assistant/website-analysis.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.00646 | $0.00646 |
| Opus 5 | $0.00323 | $0.00323 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
website-analysis 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 6d 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
100% identical to website-analysis — 0 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.
What it actually says
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
How to perform a website analysis before writing the code of a Scrapy scraper
- From the conversation, please identify the type of Scrapy spider that should be built (e.g. E-commerce PLP, E-commerce PDP, etc.) and confirm it by writing it in the chat
- Fetch the home page HTML and store it in the absolute path of the project, naming the file homepage.html, while store the cookies in the cookies.txt file
- Using the MCP tool strip_css, strip the CSS from the file homepage.html and save the new version on the file homepage_stripped.html
- Read the file cookies.txt and look for anti-bot software traces, like Akamai, Datadome, PerimeterX and so on. For every cookie name, check if it can be referred to an anti bot solution.
- If Akamai is found between the anti-bots, when creating your scraper you'll need to add the scrapy_impersonate package in the execution to make it work
- If Datadome or Kasada are found betwen the anti-bots, stop the process
- If you're asked to create an e-commerce PLP scraper, follow these steps:
- Ask for a product category URL and fetch its HTML, saving it in the absolute path of the project, with the name category.html. Store the cookies in the cookies_category.txt file.
- Using the MCP tool strip_css, strip the CSS from the file category.html and save the new version on the file category_stripped.html
- Read the file homepage_stripped.html and look for any well formatted JSON you can use to get all the product categories URL, included the one just passed. Look for schema.org but also common frameworks like Next.js. Be careful that schema.org JSON does not include the full price without discount of a product, so you'll need to look for it elsewhere.
- Read the file category_stripped.html and look for any well formatted JSON you can use to read the product details of every product on the category page. If there's any, save this JSON in a file called catalog.json
- If you're asled to create a PDP scraper, follow these steps:
- Ask for a product page and fetch its HTML, saving it in the absolute path of the project, with the name product.html. Store the cookies in the cookies_product.txt file.
- Using the MCP tool strip_css, strip the CSS from the file product.html and save the new version on the file product_stripped.html
- Read the file product_stripped.html and look for any well formatted JSON you can use to read the product details of every product on the category page. If there's any, save this JSON in a file called product.json. Look for schema.org but also common frameworks like Next.js. Be careful that schema.org JSON does not include the full price without discount of a product, so you'll need to look for it elsewhere.
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.
- 6d ago First seen · 27 lines · 646 tokens per session scan A db5004c79ad5
website-analysis is a cursor rule published in the GitHub repository Solihatun1/AI-Cursor-Scraping-Assistant (6 stars, last pushed 6mo ago), licensed MIT. It adds 646 tokens to every session, about $0.0032 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to website-analysis, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
scraper-models
Cursor rule "scraper-models" from TheWebScrapingClub/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 TheWebScrapingClub/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.
prerequisites
description: This rule provides the action that should be taken before starting implementing a Scrapy spider. globs: /.py.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.