mx: Instructions file for GitHub Copilot

.github/instructions/generated-core.instructions.md

mx generated-core.instructions.md is an instructions file for GitHub Copilot from webern/mx. It costs 165 tokens per session, scanned A, original, MIT.

Instructions for a directory containing generated files from the MusicXML code generator. MusicXML is a standard format for describing written music and its structure.

In plain words
What is it for?
Use them when reviewing changes to generated C++, Go, C, or related files: inspect the generator change first, then check the generated diff for unintended wide-reaching effects.
Why use it?
They prevent developers from editing generated output that will be overwritten during regeneration. They also require generator changes and generated results to stay in sync through a continuous-integration drift check.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

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

View source ↗ webern/mx
Reuse

Borrowing it

Nothing to install: this file belongs to webern/mx. 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/webern/mx/main/.github/instructions/generated-core.instructions.md
Clone the repo
git clone --depth 1 https://github.com/webern/mx

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 mx generated-core.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/webern/mx/generated-core"><img src="https://agentmods.dev/badge/instructions/webern/mx/generated-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 165 This file is loaded in full into every session.
When invoked 165 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.00165 $0.00165
Opus 5.5 $0.00066 $0.00066
Sonnet 5.5 $0.00033 $0.00033
Haiku 4.5 $0.00016 $0.00016

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

Security

Grade A, and why

mx generated-core.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 2mo 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/instructions/generated-core.instructions.md · 13 lines

What it actually says

Everything in this directory is GENERATED by gen/ (make gen-cpp) from the MusicXML XSD.

  • Do not review style, naming, or repetition here; the generator owns those.
  • A diff in these files must be accompanied by a change under gen/ (templates, config, or generator code) that produces it. Flag any hand edit -- it will be destroyed on the next regeneration, and the CI drift check (make gen then git diff --exit-code) fails on it.
  • Review the paired gen/ change instead, and check the generated diff only for evidence of an unintended blast radius (e.g. an edit meant for one type changing hundreds of files).
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. 2mo ago First seen · 13 lines · 165 tokens per session scan A bd9b95f8f44e

Subscribe to this mod's changes

mx generated-core.instructions.md is an instructions file published in the GitHub repository webern/mx (93 stars, last pushed yesterday), licensed MIT. It adds 165 tokens to every session, about $0.0007 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-30.

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,461 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,261 tokens