mx: Instructions file for GitHub Copilot

.github/instructions/api-headers.instructions.md

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

Review rules for public C++ headers in the mx API, which presents a simpler data model for MusicXML. The headers define plain data structures used by programs that consume the library.

In plain words
What is it for?
Use them when adding or changing public API fields, enums, positioned music data, equality definitions, or result types, especially when reshaping MusicXML concepts.
Why use it?
They help keep the public interface safe, predictable, and independent of internal types. The rules also protect equality checks, optional values, round-trip behavior, and error handling from subtle bugs.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: reads .claude/ paths.

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/api-headers.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 api-headers.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/webern/mx/api-headers"><img src="https://agentmods.dev/badge/instructions/webern/mx/api-headers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 426 This file is loaded in full into every session.
When invoked 426 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.00426 $0.00426
Opus 5.5 $0.00170 $0.00170
Sonnet 5.5 $0.00085 $0.00085
Haiku 4.5 $0.00043 $0.00043

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

Security

Grade A, and why

mx api-headers.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 1mo 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/api-headers.instructions.md · 27 lines

What it actually says

These are the public mx::api headers: plain-old-data structs that re-shape MusicXML into a simpler model (doctrine: .claude/skills/mx-api-doctrine/SKILL.md). Review for:

  • No mx::core type may appear in a public header.
  • New absent-able fields must be std::optional<T>. New absent-able enums must instead have an unspecified first enumerator (including uses of the ternary Bool). Reject new -1 sentinels and new bool is...Specified / has... flags; do not ask for migration of existing ones (tracked in issue #249).
  • Every new field needs a default value and a matching MXAPI_EQUALS_MEMBER(field) line (MXAPI_DOUBLES_EQUALS_MEMBER for doubles) in the type's equality block. A missing line silently exempts the field from equality and round-trip checks -- flag it as a bug.
  • New data must not mirror MusicXML's raw shape when the element is stateful, flat, duplicated, or id-linked; check the change against the principles doc.
  • A new positioned-in-a-measure type needs int tickTimePosition; durations are in ticks.
  • No UB or exceptions reachable through the public interface; a failed precondition must never throw. Flag new Result usage outside MusicXml, unchecked std::get, or accessors that return references guarded only by a precondition.
  • Kind-specific payloads use the choice-class pattern (TimeChoice.h, MarkDataChoice.h), not loose fields that apply only to some kinds.
  • Comments must serve a user authoring or reading notation: crisp, semantics-first, explaining how MusicXML encodes the feature. Flag round-trip framing ("the source", "preserved") except on true fidelity knobs, notes about what is not modeled, and separator/banner comments.
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. 1mo ago Changed 3a6fc543c505
  2. 2mo ago First seen · 27 lines · 426 tokens per session scan A 3db80f52514e

Subscribe to this mod's changes

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