string-le copilot-instructions.md

A Copilot instruction document that routes contributors and coding agents to AGENTS.md before they write code. It repeats rules about structure, control flow, immutability, errors, user-interface separation, and commits.

In plain words
What is it for?
Use it to guide Copilot while editing the Strings-LE project, especially before implementation and before creating commits.
Why use it?
It keeps Copilot aligned with the repository’s engineering standards and avoids inconsistent instructions across coding tools.

Instructions file for GitHub Copilot

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 instructions/nolindnaidoo/string-le/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/nolindnaidoo/string-le

Made for: GitHub Copilot.

Per session 412 This file is loaded in full into every session.
When invoked 412 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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 $0.00412 $0.00412
Opus 5 $0.00206 $0.00206
Sonnet 5 $0.00082 $0.00082
Haiku 4.5 $0.00041 $0.00041

Measured 2d ago against content hash bbdfd75b686c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

string-le copilot-instructions.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

100% identical to regex-le copilot-instructions.md — 0 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.

.github/copilot-instructions.md · 41 lines

What it actually says

Contributor and agent instructions

Read AGENTS.md before writing any code. It carries the engineering standard this repository is held to — control flow, error handling, immutability, structure — plus the architecture, the invariants and why each one exists. CLAUDE.md is the short version: gates and traps.

This file exists only to route you there. It is deliberately thin: the standard lives in one place so it cannot drift between tools.

Non-negotiables

  • Guard clauses first. No else, no else if — two branches are an early return, many are a lookup table.
  • Nesting stops at two levels inside a function.
  • Immutable by default: readonly, ReadonlyArray, Object.freeze. Never mutate a parameter.
  • Composition, never inheritance. Factory functions returning frozen objects, dependencies passed in as a typed bag.
  • Logic never touches vscode.window.*; ui/ renders and commands/ orchestrates.
  • Never report success you did not achieve — check what the API returned.
  • Errors are descriptive and never swallowed.
  • Comments explain why, never what.
  • Commits are conventional (fix:, feat:, docs:…), imperative, and enforced by a hook and by CI.

Before you commit

bun run typecheck && bun run lint && bun run test

Coverage floors are a backstop against an untested module, not a target: they sit well below where the code actually is and are never raised to track it. Every claim in a README or manifest must be provable against the code.

Provable is about behaviour and numbers, not availability. An install line for a release you are about to make is staged, not forbidden — write it, and let the release commit be what makes it true.

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 First seen · 41 lines · 412 tokens per session scan A bbdfd75b686c

Subscribe to this mod's changes

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