Borrowing it
Nothing to install: this file belongs to linuxfoundation/lfx-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/linuxfoundation/lfx-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/linuxfoundation/lfx-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/linuxfoundation/lfx-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/linuxfoundation/lfx-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/linuxfoundation/lfx-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.
<a href="https://agentmods.dev/instructions/linuxfoundation/lfx-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/linuxfoundation/lfx-mcp/copilot-instructions.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.00849 | $0.00849 |
| Opus 5.5 | $0.00340 | $0.00340 |
| Sonnet 5.5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
lfx-mcp copilot-instructions.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
purpose. Do **not** use the `gh` CLI or `curl`: the tokens in the session How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lfx-mcp — agentic review
This repo runs agentic review on its pull requests. Read the task you were given and pick the matching section. Each section names the owner (a skill or an agent) that handles that job. Follow it exactly.
1. Code review
When the task is to review a change for correctness, design, and security, use
the /copilot-code-reviewer skill and follow it exactly. Post one inline comment
per finding (each prefixed with a severity like [high]) plus a summary, through
your native review publishing (the code-review flow creates inline review threads
itself; the GitHub MCP server's write tools are for the escalation and conductor
tasks, which only add issue comments and thread replies).
2. needs-human escalation
When the task is to decide whether a PR needs a human's sign-off before merge
(the needs-human gate), use the /needs-human-escalation skill and follow it.
It decides needs-human and posts its verdict in the format defined by
/agentic-comment-format; it references the /escalation-guidelines skill.
3. Thread reconciliation / agentic-check
When the task is to check whether the AI reviewers' findings are fixed or
validly rebutted and to update the agentic gate, use the /pr-conductor skill
and follow it. It reconciles the AI-reviewer threads (never human threads), works
with the engineer on findings that go against the architecture, references
/mcp-code-review and /mcp-security-review, and posts its agentic-check
verdict in the format defined by /agentic-comment-format.
The agent tasks act through the GitHub MCP server
In the escalation and conductor tasks (sections 2 and 3 — not the code review,
which publishes inline threads through its own native review pipeline), publish
your output yourself with the add_issue_comment tool, which posts a comment
on the pull request. The conductor also has
add_reply_to_pull_request_comment to reply on a review thread (to explain
why a thread is now resolved, or why it still blocks). Those are the only write
tools configured for you; everything else in the GitHub MCP is read-only, on
purpose. Do not use the gh CLI or curl: the tokens in the session
environment (GITHUB_COPILOT_API_TOKEN, COPILOT_SDK_AUTH_TOKEN) are model/SDK
credentials and cannot write the GitHub REST API. Do not modify code, push
commits, or open a pull request. Labels, statuses, thread resolutions, and
approvals are set by deterministic workflow steps that read your comment, not by
you.
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.
- 1mo ago Changed · -31 lines · -396 tokens per session ee5e3958ab26
- 1mo 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 (21 stars, last pushed 6d ago), licensed MIT. It adds 849 tokens to every session, about $0.0034 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.