colors-le: Instructions file for Codex

AGENTS.md

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

Technical instructions for Colors-LE, a VS Code extension and Rust CLI that extract colors from CSS, markup, scripts, and SVG files. They describe the architecture, source of truth, and behavior such as sorting, filtering, conversion, and validation.

In plain words
What is it for?
Use them to navigate the codebase, follow its control flow and coding standards, and check that extraction behavior stays aligned across both products.
Why use it?
They help contributors understand which product they are changing and preserve parity between the extension and the Rust implementation.

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

Reuse

Borrowing it

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nolindnaidoo/colors-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/colors-le/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7,174 This file is loaded in full into every session.
When invoked 7,174 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 80% 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.07174 $0.07174
Opus 5.5 $0.02870 $0.02870
Sonnet 5.5 $0.01435 $0.01435
Haiku 4.5 $0.00717 $0.00717

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

Security

Grade A, and why

colors-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 2d 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

80% identical to regex-le AGENTS.md — 115 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 · 374 lines

How it starts

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

AGENTS.md — Colors-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), which ports extraction only. The shared corpus lives at crate/fixtures/; scripts/check-extraction-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 extraction engine, bundled to cli/cli.js as the npm package colors-le. Both install a command named colors-le, so the npm one is held to the crate's surface byte for byte, which is a different contract from the extraction parity above. src/cli/ follows crate/src/cli.rs, scan.rs, walk.rs and extract/palette.rs, not the extension's commands, and scripts/check-cli-parity.ts runs both binaries over one generated tree and fails on any difference in stdout, stderr or exit code, and in what colors-le mcp answers. 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 extracts colors from the active document (CSS/SCSS/LESS/Stylus, HTML, JS/TS, SVG) into a results editor, with dedupe/sort/convert/filter/analyze/validate post-processing. No network access, no filesystem writes.

Architecture

extension.ts            activate(): createServices() -> registerCommands()
services/serviceFactory createServices(context) -> { telemetry, notifier, statusBar }
commands/               one file per command; extract/dedupe/sort/help take the
                        frozen deps bag; analyze/convert/filter/validate are
                        self-contained (vscode UI + performance.now timing)
extraction/extract.ts   dispatcher: languageId -> FileType -> extractor
extraction/heuristics.ts  THE color patterns/validators: hex + functional
                        regexes, NAMED_COLORS set, comment blanking,
                        declaration-value segmentation, string-literal spans
extraction/position.ts    offset -> {line, column} via newline index (1-based)
extraction/formats/     stylesheet.ts (css/scss/less/stylus), markup.ts
                        (html/svg), javascript.ts — all offset-based
analysis/colorAnalysis  statistics/clusters/patterns for the Analyze command
conversion/colorConverter  convert/validate engines (hex/rgb/hsl, contrast)
ui/                     notifier (window messages, gated by notificationsLevel:
                        all -> everything, important -> warn+error, silent -> error only),
                        statusBar
utils/                  errors (sanitizeErrorMessage), safety (size guards),
                        colorConversion (parse/convert primitives), dedupe,
                        sort, format (formatDuration)
config/config.ts        getConfiguration() snapshot; CONFIG_DEFAULTS table
types.ts                shared types only — no logic
cli/                    the npm command line: args, walk + ignoreRules
                        (ripgrep's precedence), palette, scan, run, and
                        scanTool for `colors-le mcp`. No `vscode`, ever

Read the full file on GitHub · 374 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. 2d ago Changed · +5 lines · +414 tokens per session 76f5849fd1d2
  2. 9d ago Changed · +49 tokens per session c85676708ab2
  3. 11d ago Changed · +11 lines · +639 tokens per session 657a87f4f329
  4. 13d ago Changed · +54 tokens per session 3e39dac9203b
  5. 19d ago Changed · +1 lines · +354 tokens per session bffbe6c90a37
  6. 22d ago Changed · -6 lines · -182 tokens per session 47934b9f5644
  7. 25d ago Changed · +21 tokens per session 080486e71b9a
  8. 27d ago Changed · +74 tokens per session fa810c548043
  9. 28d ago Changed · +19 lines · +303 tokens per session bd56f5ccc659
  10. 1mo ago First seen · 344 lines · 5,448 tokens per session scan A ad76c3a223ec

Subscribe to this mod's changes

colors-le AGENTS.md is an instructions file published in the GitHub repository nolindnaidoo/colors-le (1 stars, last pushed 3d ago), licensed MIT. It adds 7,174 tokens to every session, about $0.0287 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to regex-le AGENTS.md, differing in 115 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,715 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,786 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