scrape-url

A command that fetches a web page from a URL and converts its contents into Markdown, a plain-text format an agent can read.

In plain words
What is it for?
Use it to read a documentation page or other URL, then answer questions or return relevant content and source links.
Why use it?
It lets the agent inspect current page content instead of relying on memory or invented details. It is intended for a one-time page check.

Command

Install

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.

agentmods
npx agentmods add commands/context-dot-dev/cursor-plugin/scrape-url
Clone the repo
git clone --depth 1 https://github.com/context-dot-dev/cursor-plugin
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00160
Opus 5 $0.00012 $0.00080
Sonnet 5 $0.00005 $0.00032
Haiku 4.5 $0.00002 $0.00016

Measured yesterday against content hash 98b07d41af5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scrape-url 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 yesterday.

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.

commands/scrape-url.md · 13 lines

What it actually says

Scrape a URL to markdown

  1. Obtain the full URL from the user (must include scheme, e.g. https://example.com/docs).
  2. Confirm the context MCP server is enabled and authenticated. If authentication is required, use the connect-context-dev skill.
  3. Call web-scrape-markdown with the URL.
  4. Return the relevant Markdown or answer the user's question from it. Preserve source links when useful.
  5. Do not fabricate page content. If the scrape fails, report the actual error and suggest a narrower selector, a longer timeout, or a retry only when appropriate.
Changes

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.

  1. yesterday First seen · 13 lines · 23 tokens per session scan A 98b07d41af5e

Subscribe to this mod's changes

scrape-url is a command published in the GitHub repository context-dot-dev/cursor-plugin (4 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 160 once invoked, about $0.0001 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-31.