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 instructions/nolindnaidoo/dates-le/agents-mdgit clone --depth 1 https://github.com/nolindnaidoo/dates-leWrote 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/instructions/nolindnaidoo/dates-le/agents-md)<a href="https://agentmods.dev/instructions/nolindnaidoo/dates-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/dates-le/agents-md.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 | $0.05215 | $0.05215 |
| Opus 5 | $0.02608 | $0.02608 |
| Sonnet 5 | $0.01043 | $0.01043 |
| Haiku 4.5 | $0.00522 | $0.00522 |
Grade A, and why
dates-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.
This is a copy
91% identical to regex-le AGENTS.md — 76 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.
How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Dates-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.
What this is
A VS Code extension that extracts dates and timestamps from the active document into a results editor, with analyze/convert/filter/validate/dedupe/sort post-processing. JSON, YAML, CSV, XML, logs/plaintext, JS/TS, HTML, TOML and Markdown are languages it names; every other languageId is read with the patterns they all share, because a format only ever adds patterns to those and returning nothing was indistinguishable from a document with no dates in it. No network access, no filesystem writes.
Architecture
extension.ts activate(): createServices() -> registerCommands()
services/serviceFactory createServices(context) -> { telemetry, notifier, statusBar }
commands/ one file per command; deps injected as a frozen bag
extraction/extract.ts dispatcher: languageId -> FileType -> extractor
extraction/heuristics.ts THE date-pattern core: BASE_PATTERNS + scanDates()
(whole-content d-flag regex, offset-containment dedupe,
instant gate — NaN timestamps are never emitted)
extraction/extended.ts the shapes Date.parse refuses (ISO week/ordinal/basic,
six timezone abbreviations), each normalised into one
it does read. Mirrored by crate/src/extract/extended.rs
extraction/position.ts offset -> {line, column} via newline index (1-based)
extraction/formats/*.ts per-format extractors; json/yaml/csv are plain
scanDates, xml masks comments first, log/js/html add
format-specific DatePatternSpec lists
analysis/statistics.ts analyzeDates(): stats, anomalies, patterns, clusters, gaps
conversion/dateConverter.ts convertDates() + getAvailableFormats()
ui/ notifier (window messages, gated by notificationsLevel:
all -> everything, important -> warn+error, silent -> error only),
statusBar
utils/ errors (sanitizeErrorMessage), safety (size guard)
config/config.ts getConfiguration() snapshot; CONFIG_DEFAULTS table
types.ts shared types only — no logic
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.
- 3d ago First seen · 323 lines · 5,215 tokens per session scan A 56e103c10b12
dates-le AGENTS.md is an instructions file published in the GitHub repository nolindnaidoo/dates-le (1 stars, last pushed 9d ago), licensed MIT. It adds 5,215 tokens to every session, about $0.0261 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to regex-le AGENTS.md, differing in 76 lines, and is treated as a copy.
Other instructions, from other repositories
tika AGENTS.md
AGENTS.md instructions for apache/tika, covering agent guidance for apache tika, local overrides, working on tika, using tika and security.
regex-le AGENTS.md
Instructions for nolindnaidoo/regex-le, covering agents.md — regex-le, what this is, architecture, code style and control flow.
regex-le CLAUDE.md
Instructions for nolindnaidoo/regex-le, covering claude.md, where to look, gates and things that will bite you.
regex-le copilot-instructions.md
Instructions for nolindnaidoo/regex-le, covering contributor and agent instructions, non-negotiables and before you commit.
envsync-le AGENTS.md
AGENTS.md instructions for nolindnaidoo/envsync-le, covering agents.md — envsync-le, what this is, architecture, code style and control flow.
colors-le AGENTS.md
Instructions for nolindnaidoo/colors-le, covering agents.md — colors-le, what this is, architecture, code style and control flow.