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/linuxfoundation/lfx-mcp/copilot-instructionsgit clone --depth 1 https://github.com/linuxfoundation/lfx-mcpWhat 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.01245 | $0.01245 |
| Opus 5 | $0.00622 | $0.00622 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
lfx-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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — LFX MCP Server
What This Repository Does
This is the LFX MCP Server — a Model Context Protocol (MCP) implementation in Go that exposes the Linux Foundation's LFX platform as MCP tools for AI agents. It uses the official MCP Go SDK and supports JSON-RPC 2.0 over stdio (dev) and Streamable HTTP (production) transports.
Key facts: ~25 Go source files, single binary, no database, stateless HTTP mode. Go and MCP SDK versions are pinned in go.mod. Built with ko for container images. Deployed to Kubernetes via Helm.
CI Rules (what breaks the build)
Two workflows run on every PR (.github/workflows/):
license-header-check.yml— tracked source/config files (Go, YAML, shell, Makefile, etc.) must begin with the license header.mega-linter.yml— MegaLinter Go flavor v9 (config:.mega-linter.yml).
Requirements for new/modified files
License header — always include as the first lines:
// Copyright The Linux Foundation and contributors.
// SPDX-License-Identifier: MIT
For YAML, shell, and Makefile use # comment syntax. Missing headers are the #1 cause of CI failure.
Package doc comment — every non-test .go file must have // Package <name> ... immediately above the package declaration. The GO_REVIVE linter enforces the package-comments rule. _test.go files are exempt.
YAML formatting — keep lines ≤120 characters (config: .yamllint); this is a warning, not a build failure. Helm templates in charts/lfx-mcp/templates/ are excluded from YAML linting.
Other MegaLinter checks: the Go flavor bundles a full set of Go and common scripting/CI linters (shell, Docker, GitHub Actions, Helm, Markdown, secrets, etc.) and runs them all by default. .mega-linter.yml is the single source of truth for what's disabled or downgraded to error-only — check it rather than relying on any list here.
Project Layout
cmd/lfx-mcp-server/main.go — Entry point, config, flag parsing, tool registration
internal/tools/ — All MCP tool implementations (one file per tool/domain)
internal/tools/scopes.go — Scope constants (ScopeRead, ScopeManage)
internal/tools/helpers.go — Shared utilities for tool handlers
internal/auth/ — JWT verification, API-key verification
internal/lfxv2/ — LFX V2 API client (token exchange, slug resolver, access checks)
internal/serviceapi/ — Generic HTTP client for downstream service APIs
internal/otel/ — OpenTelemetry initialization
charts/lfx-mcp/ — Helm chart (deployment, ingress, service, PDB)
Makefile — Build automation (targets: build, test, check, clean, etc.)
.mega-linter.yml — MegaLinter config
.yamllint — YAML lint rules (max line length: 120)
.ko.yaml — ko builder config with ldflags
Dockerfile — Multi-stage build (Chainguard base images)
AGENTS.md — Detailed developer guide (canonical; CLAUDE.md is a symlink)
ARCHITECTURE.md — System architecture with Mermaid diagrams
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.
- 2d ago First seen · 97 lines · 1,245 tokens per session scan A f3aed78f272b
lfx-mcp copilot-instructions.md is an instructions file published in the GitHub repository linuxfoundation/lfx-mcp (20 stars, last pushed 4d ago), licensed MIT. It adds 1,245 tokens to every session, about $0.0062 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.