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.
curl -O https://raw.githubusercontent.com/abossard/ledfx-mcp/main/AGENTS.mdgit 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/agents-md)<a href="https://agentmods.dev/instructions/abossard/ledfx-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/abossard/ledfx-mcp/agents-md/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.
<a href="https://agentmods.dev/instructions/abossard/ledfx-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/abossard/ledfx-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00769 | $0.00769 |
| Opus 5.5 | $0.00308 | $0.00308 |
| Sonnet 5.5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
ledfx-mcp AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Rules (Repository-Wide)
Skills
A skill is a set of local instructions to follow that is stored in a SKILL.md file. Below is the list of skills that can be used in this repository.
Available skills
- blender-archetype-library: Apply reusable blender scene archetypes (wobble, flow, hard, bullet) with controlled layer behavior. Use when designing or refactoring LedFX blender scenes and masks for readable yet high-impact DJ visuals. (file: /Users/abossard/Desktop/projects/ledfx-mcp/skills/blender-archetype-library/SKILL.md)
- dj-phase-composer: Compose phase-based DJ lighting scenes from creative rules into executable direct and blender scene specs. Use when translating a DJ guide into LedFX scene blueprints, role ordering, or phase playlist flows. (file: /Users/abossard/Desktop/projects/ledfx-mcp/skills/dj-phase-composer/SKILL.md)
- ledfx-mcp-tooling: Build or debug LedFX automations through MCP tools with schema-safe effect configs, fallback chains, and palette/gradient validation. Use when writing scripts or commands that call
ledfx_*tools, especiallyset_effect,set_blender, scene, or playlist operations. (file: /Users/abossard/Desktop/projects/ledfx-mcp/skills/ledfx-mcp-tooling/SKILL.md) - playlist-variety-auditor: Audit DJ lighting playlists for effect-family diversity, strobe density, phase coverage, and role balance. Use when validating that playlists are not repetitive and comply with guide constraints before showtime. (file: /Users/abossard/Desktop/projects/ledfx-mcp/skills/playlist-variety-auditor/SKILL.md)
- rapid-flow-designer: Design rapid directional lighting scenes that read as lightning-bullet motion with controlled intensity. Use when creating high-velocity LED looks with scroll/scan carriers and safe duration/pacing constraints. (file: /Users/abossard/Desktop/projects/ledfx-mcp/skills/rapid-flow-designer/SKILL.md)
How to use skills
- Discovery: The list above is the skills available in this repository session (name + description + file path). Skill bodies live on disk at the listed paths.
- Trigger rules: If the user names a skill (with
$SkillNameor plain text) OR the task clearly matches a skill description shown above, use that skill for that turn. Multiple mentions mean use them all. Do not carry skills across turns unless re-mentioned. - Missing/blocked: If a named skill path cannot be read, say so briefly and continue with the best fallback.
- How to use a skill (progressive disclosure):
- Open its
SKILL.mdand read only enough to execute the workflow. - Resolve relative paths in a skill relative to that skill directory first.
- Load only the specific extra files needed (
references/,assets/, etc), not the entire folder. - If
scripts/exist in the skill, prefer running or patching them over rewriting large blocks. - Reuse templates/assets from skills when available.
- Open its
- Coordination and sequencing:
- If multiple skills apply, choose the minimal set that covers the task and state the order.
- Announce which skill(s) are being used and why in one short line.
- Context hygiene:
- Keep context small: summarize large sections and load only required files.
- Avoid deep reference-chasing unless blocked.
- Safety and fallback: If a skill is unclear or incomplete, state the issue, choose the next-best approach, and continue.
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.
- 2mo ago First seen · 30 lines · 769 tokens per session scan A 927e7cbd6897
ledfx-mcp AGENTS.md is an instructions file published in the GitHub repository abossard/ledfx-mcp (4 stars, last pushed 4mo ago), licensed MIT. It adds 769 tokens to every session, about $0.0031 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.
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).
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.
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).
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.
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).
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.