scrape-le: Instructions file for Codex

AGENTS.md

scrape-le AGENTS.md is an instructions file for Codex, OpenCode from nolindnaidoo/scrape-le. It costs 6,948 tokens per session, scanned A, a copy of regex-le AGENTS.md, MIT.

Repository instructions for coding agents working on Scrape-LE, a VS Code extension and Rust command-line tool that inspect whether a website can be scraped.

In plain words
What is it for?
Use them when modifying URL checks, anti-bot detection, robots.txt handling, authentication checks, screenshots, shared signatures, or the Rust CLI.
Why use it?
They explain the project’s structure, rules, shared test data, and network limits so changes do not make the two products disagree or access unrelated sites.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

This is nolindnaidoo/scrape-le's own configuration. It tells Codex and OpenCode how to work on scrape-le itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything scrape-le configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nolindnaidoo/scrape-le. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nolindnaidoo/scrape-le/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/nolindnaidoo/scrape-le

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for scrape-le AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nolindnaidoo/scrape-le/agents-md/github.svg)](https://agentmods.dev/instructions/nolindnaidoo/scrape-le/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/nolindnaidoo/scrape-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/scrape-le/agents-md/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.

agentmods 80×15 button for scrape-le AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nolindnaidoo/scrape-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/scrape-le/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,948 This file is loaded in full into every session.
When invoked 6,948 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod 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.1 $0.06948 $0.06948
Opus 5.5 $0.02779 $0.02779
Sonnet 5.5 $0.01390 $0.01390
Haiku 4.5 $0.00695 $0.00695

Measured 3d ago against content hash f611bb571f99, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scrape-le AGENTS.md 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 3d 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.

Origin

This is a copy

83% identical to regex-le AGENTS.md — 127 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.

AGENTS.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — Scrape-LE

Technical source of truth for this repo. README.md is the user-facing doc; this file is for anyone (human or agent) changing the code.

This repo hosts two products: the extension at the root (this document's scope) and the Rust CLI in crate/ (its own AGENTS.md + SPEC.md). The shared detection corpus lives at signatures/ and fixtures/; scripts/check-signature-parity.ts fails CI when this extension drifts from it.

The Rust CLI also ships a second way, through npm: src/cli/ is its terminal surface rebuilt over this extension's vendor table and robots.txt encoding, bundled to cli/cli.js as the npm package scrape-le. Both install a command named scrape-le, so the npm one is held to the crate's surface byte for byte, which is a different contract from the corpus parity above. src/cli/ follows crate/src/cli.rs, check_url.rs, fetch.rs, render.rs, batch.rs, detect/ and mcp/, not the extension's commands: it speaks HTTP/1.1 over a socket the way ureq does, launches Chrome with headless_chrome's flags and drives it over --remote-debugging-pipe, and writes JSON the way serde_json does. scripts/check-cli-parity.ts runs both binaries against one loopback fixture server, rendered and not, and fails on any difference in stdout, stderr, exit code, screenshot name, or what scrape-le mcp answers. Only timings are masked, and the wording of a TOML or JSON parse error the crate's parsers render. scripts/check-cli-pipes.ts, shared with every port, closes stdout or stderr before either binary writes and fails on any difference in what follows, on all three operating systems. A change to the crate's surface changes src/cli/ in the same commit.

What this is

A VS Code extension that loads a URL in headless Chromium (playwright-core) and reports what would block a scraper: HTTP status/title/load time, console errors, a full-page screenshot, anti-bot vendor detection, rate-limit headers, robots.txt evaluation, and authentication walls. Network access is scoped to the URL under check plus that origin's /robots.txt — nothing else, ever.

Read the full file on GitHub · 368 lines

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. 3d ago Changed · +49 tokens per session f611bb571f99
  2. 5d ago Changed · +14 lines · +821 tokens per session 7a09cbe3c281
  3. 7d ago Changed · +54 tokens per session f0c21c173b41
  4. 13d ago Changed · +1 lines · +354 tokens per session 469bc4fb4e7d
  5. 15d ago Changed · -6 lines · -182 tokens per session 04ebd4c73fb4
  6. 20d ago Changed · -2 lines · -26 tokens per session d4af4644f36d
  7. 21d ago Changed · +19 lines · +377 tokens per session f87536e40e3b
  8. 1mo ago First seen · 342 lines · 5,501 tokens per session scan A 3a951f0a4cb3

Subscribe to this mod's changes

scrape-le AGENTS.md is an instructions file published in the GitHub repository nolindnaidoo/scrape-le (1 stars, last pushed 3d ago), licensed MIT. It adds 6,948 tokens to every session, about $0.0278 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to regex-le AGENTS.md, differing in 127 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,384 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens