claude-dev-env: Instructions file for GitHub Copilot

.github/copilot-instructions.md

claude-dev-env copilot-instructions.md is an instructions file for GitHub Copilot from jl-cmd/claude-dev-env. It costs 736 tokens per session, scanned A, original, MIT.

Editor instructions for an AI coding assistant working in a JavaScript or TypeScript project. They define naming, comment, documentation, type, and configuration rules enforced by automated checks.

In plain words
What is it for?
Use them when naming variables or functions, writing comments, documenting code, defining types, or changing configuration in the project.
Why use it?
They make suggestions predictable and help code pass the project's review and validation checks.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is jl-cmd/claude-dev-env's own configuration. It tells GitHub Copilot how to work on claude-dev-env 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 claude-dev-env configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jl-cmd/claude-dev-env. 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/jl-cmd/claude-dev-env/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/jl-cmd/claude-dev-env

Made for: GitHub Copilot.

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 claude-dev-env copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jl-cmd/claude-dev-env/copilot-instructions/github.svg)](https://agentmods.dev/instructions/jl-cmd/claude-dev-env/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/jl-cmd/claude-dev-env/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jl-cmd/claude-dev-env/copilot-instructions/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 claude-dev-env copilot-instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jl-cmd/claude-dev-env/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jl-cmd/claude-dev-env/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 736 This file is loaded in full into every session.
When invoked 736 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 original No closer match found 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.00736 $0.00736
Opus 5.5 $0.00294 $0.00294
Sonnet 5.5 $0.00147 $0.00147
Haiku 4.5 $0.00074 $0.00074

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

Security

Grade A, and why

claude-dev-env 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 13d 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.

.github/copilot-instructions.md · 49 lines

How it starts

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

Copilot instructions

Hooks in this repo enforce the conventions below. Follow them so your suggestions match what the gates accept.

Canonical review contract: packages/claude-dev-env/docs/CODE_RULES.md. Checked-in pointer: .cursor/BUGBOT.md.

Naming

  • Full words, no abbreviations. Never name anything ctx, cfg, msg, btn, idx, cnt, tmp, elem, or val — write context, configuration, message, button, index, count, element, and so on.
  • Never use the vague names result, data, output, response, value, item, or temp. Pick a domain noun that says what the thing is.
  • Never start a function name with handle_, process_, manage_, or do_. Name the action: validate_order, send_invite, build_prompt.
  • Boolean names start with is_, has_, should_, can_, was_, or did_ (camelCase is / has / should / can / was / did in JavaScript and TypeScript).
  • Loop variables read as each_<noun>. The single letters i, j, k are fine for numeric loops and e for a caught exception.

Comments and documentation

  • Do not add code comments. Preserve existing comments. Docstrings remain allowed.
  • When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
  • Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
  • Docstrings on modules, classes, and functions are welcome. Keep the prose in step with the code: a docstring that lists the cases the body handles lists every one of them.
  • Never drop an existing comment on a line you are not otherwise changing.
  • Documentation describes the current state of the code. State what the code is and does.

Types

  • Every function parameter and every return is typed.
  • Do not use Any, do not use cast(), or add # type: ignore; remove the escape hatch and use a typed boundary or real type.

Read the full file on GitHub · 49 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. 13d ago Changed · -4 tokens per session aae1d084cf2e
  2. 1mo ago Changed · +2 lines · +62 tokens per session 3925da8c8754
  3. 1mo ago First seen · 47 lines · 678 tokens per session scan A 79831627ca8b

Subscribe to this mod's changes

claude-dev-env copilot-instructions.md is an instructions file published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 13d ago), licensed MIT. It adds 736 tokens to every session, about $0.0029 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

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,257 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens