tc39-mcp: Instructions file for GitHub Copilot

.github/copilot-instructions.md

tc39-mcp copilot-instructions.md is an instructions file for GitHub Copilot from xyzzylabs/tc39-mcp. It costs 747 tokens per session, scanned A, original, MIT.

Repository instructions for maintaining a read-only server that provides structured access to JavaScript language specifications through the Model Context Protocol.

In plain words
What is it for?
Use them when changing or reviewing tools for searching specifications, cross-references, edition differences, test262 tests, or proposal data.
Why use it?
They explain the project's boundaries and help reviewers protect its fixed data, narrow tool set, and no-write design.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is xyzzylabs/tc39-mcp's own configuration. It tells GitHub Copilot how to work on tc39-mcp 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 tc39-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xyzzylabs/tc39-mcp. 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/xyzzylabs/tc39-mcp/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/xyzzylabs/tc39-mcp

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 tc39-mcp copilot-instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xyzzylabs/tc39-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/xyzzylabs/tc39-mcp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 747 This file is loaded in full into every session.
When invoked 747 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.00747 $0.00747
Opus 5 $0.00374 $0.00374
Sonnet 5 $0.00149 $0.00149
Haiku 4.5 $0.00075 $0.00075

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

Security

Grade A, and why

tc39-mcp 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 8d 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 · 63 lines

How it starts

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

Copilot instructions for tc39-mcp

Guidance for GitHub Copilot — including Copilot code review — in this repository.

The authoritative rules live in AGENTS.md (the cross-tool agent contract; CLAUDE.md and this file defer to it). Read it first. The notes below restate the invariants a review should enforce and flag the patterns that are intentional here, so reviews stay signal-heavy.

What this project is

A read-only, public MCP server for the TC39 specs (ECMA-262 + ECMA-402). It exposes structured clauses, AOID-aware search, in+out cross-references, edition diffs, git history, test262 search, and proposal lookup over the Model Context Protocol — locally over stdio or hosted as a Cloudflare Worker over HTTP. Data is SHA-pinned and auto-refreshes from the upstream tc39/* mains. The server is the product: code, dependencies, and docs read as if written for any reader of the TC39 specs, not one downstream consumer.

When reviewing, enforce these invariants

  1. The tool surface stays narrow. Every tool is read-only, deterministic, and a pure function of SHA-pinned data — no execution, no auth, no writes, no user-supplied code. Flag any new tool or schema change that breaks this.
  2. Nothing hosted-incompatible in the tool surface. No shell-out, network call, or filesystem write that can't run behind a Cloudflare Worker. The only subprocess in the whole server is spec.history's git log against a vendored checkout — flag any new one.
  3. Comments and docs describe the code, in general terms. Flag anything that only makes sense to a specific downstream consumer; it should describe the general behavior instead.
  4. Schemas are the contract. Input schemas use Zod; every exported interface field carries a JSDoc comment (the /tools page is generated from these). A tool-schema change is breaking — flag a missing CHANGELOG.md entry.
  5. docs/tools.md is generated by npm run docs:data from the schemas — never hand-edited. Flag manual edits.
  6. Tests are co-located as *.test.ts (worker tests under worker/src/**). A new tool needs a unit test and, after regeneration, a docs/tools.md section.

Read the full file on GitHub · 63 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. 8d ago First seen · 63 lines · 747 tokens per session scan A a74b63b808ca

Subscribe to this mod's changes

tc39-mcp copilot-instructions.md is an instructions file published in the GitHub repository xyzzylabs/tc39-mcp (2 stars, last pushed yesterday), licensed MIT. It adds 747 tokens to every session, about $0.0037 per session on Opus 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

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