urls-le: Instructions file for Codex

AGENTS.md

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

Project instructions for URLs-LE, a VS Code extension and Rust command-line tool that extracts web addresses and other link types from documents. VS Code is a code editor, and Rust is a programming language.

In plain words
What is it for?
Use them when changing URL extraction, maintaining parity between the extension and Rust tool, or working on the shared test fixtures and MCP server.
Why use it?
They explain the project structure, supported document formats, testing requirements, and the rule that extracted links are read from text rather than fetched online.

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/urls-le's own configuration. It tells Codex and OpenCode how to work on urls-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 urls-le configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nolindnaidoo/urls-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/urls-le/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/nolindnaidoo/urls-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 urls-le AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nolindnaidoo/urls-le/agents-md.svg)](https://agentmods.dev/instructions/nolindnaidoo/urls-le/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/nolindnaidoo/urls-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/urls-le/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 5,473 This file is loaded in full into every session.
When invoked 5,473 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 86% 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.05473 $0.05473
Opus 5 $0.02736 $0.02736
Sonnet 5 $0.01095 $0.01095
Haiku 4.5 $0.00547 $0.00547

Measured 6d ago against content hash b3aad78d8ed8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

86% identical to regex-le AGENTS.md — 95 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 · 338 lines

How it starts

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

AGENTS.md — URLs-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 extraction corpus lives at crate/fixtures/; scripts/check-extraction-parity.ts fails CI when this extension drifts from it.

What this is

A VS Code extension that extracts URLs (http/https/ftp/file/mailto/tel) from the active document — any document — into a results editor, with dedupe/sort post-processing. Markdown, HTML, CSS, JS/TS, JSON, YAML, Properties, TOML, INI and XML know what to exclude; every other languageId is scanned whole. No network access — URLs are read from text, never fetched or validated.

Architecture

extension.ts            activate(): createServices() -> registerCommands()
services/serviceFactory createServices(context) -> { telemetry, notifier, statusBar }
commands/               one file per command; deps injected as a frozen bag
mcp/                    MCP server: transport.ts holds the hand-rolled
                        protocol (one swap seam), tools.ts the tool table,
                        envelope.ts the normalisation boundary, fileType.ts a
                        tolerant format resolver. Imports the engine only —
                        never vscode. provider.ts is the one exception: it is
                        the VS Code side, offering the built server to agent
                        mode, and is not part of the server bundle.
extraction/extract.ts   dispatcher: languageId -> FileType -> extractor;
                        content-size cap (10MB), URL-count cap (50k), unknown
                        languages take the plain-text scan (no refusal)
extraction/heuristics.ts  THE single URL scanner: five protocol patterns,
                        scanUrls() -> UrlMatch[], toUrls() enrichment,
                        locateParsedValues() for parser-based formats
extraction/position.ts    offset -> {line, column} via newline index (1-based)
extraction/formats/*.ts   one extractor per format; scan-based ones filter the
                        shared scan (markdown: code regions, html: comments,
                        properties: comment lines), parser-based ones
                        (json/toml/ini) walk tokens or values, and
                        plaintext.ts is the unfiltered scan every other
                        languageId gets
ui/                     notifier (window messages, gated by notificationsLevel:
                        all -> everything, important -> warn+error, silent ->
                        error only), statusBar
utils/                  errors (sanitizeErrorMessage), safety (size guard +
                        large-file warning)
config/config.ts        getConfiguration() snapshot; CONFIG_DEFAULTS table
types.ts                shared types only — no logic

Read the full file on GitHub · 338 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. 6d ago First seen · 338 lines · 5,473 tokens per session scan A b3aad78d8ed8

Subscribe to this mod's changes

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

Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens