Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/abossard/ledfx-mcp/copilot-instructionsgit clone --depth 1 https://github.com/abossard/ledfx-mcpWrote 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.
[](https://agentmods.dev/instructions/abossard/ledfx-mcp/copilot-instructions)<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="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01101 | $0.01101 |
| Opus 5 | $0.00550 | $0.00550 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
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 3d 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.
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":
-
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.
-
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
-
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:
-
Deep Modules
- Create modules with simple interfaces that hide complex implementations
- The LedFxClient is a good example: simple methods hide HTTP complexity
-
Information Hiding
- Hide implementation details
- Expose only what's necessary for the module's purpose
- Example: HTTP details are hidden inside LedFxClient methods
-
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
interfaceovertypefor object shapes - Use strict TypeScript settings
- Avoid
any- useunknownwhen 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
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.
- 3d ago First seen · 156 lines · 1,101 tokens per session scan A 05a1eaeccd54
ledfx-mcp copilot-instructions.md is an instructions file published in the GitHub repository abossard/ledfx-mcp (4 stars, last pushed 2mo ago), licensed MIT. It adds 1,101 tokens to every session, about $0.0055 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.
Other instructions, from other repositories
firmware CLAUDE.md
Claude Code instructions for OpenIPC/firmware, covering claude.md, what this is, before you start: is this the right repository?, build and common tasks.
Tutorial_AwesomeModernCPP AGENTS.md
AGENTS.md instructions for Awesome-Embedded-Learning-Studio/Tutorial_AwesomeModernCPP, covering agents.md, 这是什么, 通用 essentials(所有 agent 必读) and 你来做什么?(按场景路由).
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
NeoMind CLAUDE.md
Instructions for camthink-ai/NeoMind, covering neomind — edge ai platform for iot, development commands, ecosystem repositories, extension package contract (.nep) and device type template contract (json).
AMD-BC-250-Windows-Driver AGENTS.md
Instructions for Keshas-dev/AMD-BC-250-Windows-Driver, covering amd bc-250 windows driver — agent notes, host machine, ⚠️ historical-data caution (2026-08-21, strengthened), fresh re-verifications (current build, 2026-08-21) and workspace boundary.
zmk-config AGENTS.md
AGENTS.md instructions for urob/zmk-config, covering customization guide, ground rules, how the multi-board layout works, adding a new board and where to change what.