ledfx-mcp: Instructions file for GitHub Copilot

.github/copilot-instructions.md

ledfx-mcp copilot-instructions.md is an instructions file for GitHub Copilot from abossard/ledfx-mcp. It costs 1,101 tokens per session, scanned A, original, MIT.

Repository instructions for LedFX MCP, a TypeScript server that lets AI assistants control LedFX, software for managing LED lighting systems.

In plain words
What is it for?
Use them when changing LedFX controls, the MCP server, the HTTP client, tools, or the TypeScript project structure.
Why use it?
They set rules for separating external actions from data processing and for keeping the protocol, tools, client, and web API layers organised.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

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

Reuse

Borrowing it

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/abossard/ledfx-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/abossard/ledfx-mcp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,101 This file is loaded in full into every session.
When invoked 1,101 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.01101 $0.01101
Opus 5.5 $0.00440 $0.00440
Sonnet 5.5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

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

Security

Grade A, and why

ledfx-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 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/copilot-instructions.md · 156 lines

How it starts

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

GitHub Copilot Instructions for LedFX MCP Server

Project Overview

This is a Model Context Protocol (MCP) server for controlling LedFX LED lighting systems. The project is written in TypeScript and follows specific software design principles.

Core Principles

Grokking Simplicity

When writing code for this project, follow these principles from "Grokking Simplicity":

  1. Separate Actions from Calculations

    • Actions: Functions that perform I/O (API calls, file operations, logging). These have side effects.
    • Calculations: Pure functions that transform data without side effects.
    • Clearly comment which functions are actions vs calculations.
  2. Stratified Design

    • Build in layers: MCP protocol → Tools → Client → HTTP API
    • Higher layers should call lower layers, never the reverse
    • Each layer should be a complete abstraction
  3. Minimize Implicit Inputs

    • Prefer explicit function parameters over global state
    • Document any necessary shared state clearly

A Philosophy of Software Design

When designing modules and interfaces:

  1. Deep Modules

    • Create modules with simple interfaces that hide complex implementations
    • The LedFxClient is a good example: simple methods hide HTTP complexity
  2. Information Hiding

    • Hide implementation details
    • Expose only what's necessary for the module's purpose
    • Example: HTTP details are hidden inside LedFxClient methods
  3. Minimize Complexity

    • Each module should have a single, focused purpose
    • Keep interfaces narrow and well-defined
    • Avoid exposing unnecessary details

Code Style Guidelines

TypeScript

  • Always use explicit return types for functions
  • Prefer interface over type for object shapes
  • Use strict TypeScript settings
  • Avoid any - use unknown when type is truly unknown

Comments

  • Use JSDoc comments for public functions and classes
  • Include brief implementation notes for complex logic
  • Document which functions are "actions" vs "calculations"
  • Explain design decisions when they're not obvious

Read the full file on GitHub · 156 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. 2mo ago First seen · 156 lines · 1,101 tokens per session scan A 05a1eaeccd54

Subscribe to this mod's changes

ledfx-mcp copilot-instructions.md is an instructions file published in the GitHub repository abossard/ledfx-mcp (4 stars, last pushed 4mo ago), licensed MIT. It adds 1,101 tokens to every session, about $0.0044 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,719 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,516 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 · 3,093 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,313 tokens