What is mcp-foundry copilot-instructions.md?

A set of instructions for GitHub Copilot, an AI coding assistant, to create or update project README files in a fixed structure.

Generating README files with sections such as an overview, installation, configuration, usage, testing, deployment, and contributing.

It removes guesswork about which sections a README should contain and the order they should use.

How Mahima-Sanketh-Git/mcp-foundry configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to Mahima-Sanketh-Git/mcp-foundry. 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/Mahima-Sanketh-Git/mcp-foundry/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/Mahima-Sanketh-Git/mcp-foundry

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/mahima-sanketh-git/mcp-foundry/copilot-instructions/github.svg)](https://agentmods.dev/instructions/mahima-sanketh-git/mcp-foundry/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/mahima-sanketh-git/mcp-foundry/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mahima-sanketh-git/mcp-foundry/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/mahima-sanketh-git/mcp-foundry/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mahima-sanketh-git/mcp-foundry/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,421 This file is loaded in full into every session.

When invoked 1,421 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.

Model	Per session	Once invoked
Fable 5.1	$0.01421	$0.01421
Opus 5.5	$0.00568	$0.00568
Sonnet 5.5	$0.00284	$0.00284
Haiku 4.5	$0.00142	$0.00142

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

Security

Grade A, and why

mcp-foundry 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 · 187 lines

How it starts

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

GitHub Copilot Instructions — Industry Standard README Generator

Place this file at .github/copilot-instructions.md in your repository. Copilot will automatically pick it up as workspace context.

🧭 Instructions for Copilot

When I ask you to generate, create, or update a README, follow every rule in this file precisely.

📋 README Structure (Always follow this exact order)

Generate a README with these sections in this order — skip a section only if there is genuinely no relevant content for it:

1.  Project Banner / Hero (badges + title + tagline)
2.  Table of Contents
3.  Overview
4.  Features
5.  Tech Stack
6.  Project Structure
7.  Prerequisites
8.  Installation
9.  Configuration (.env / environment variables)
10. Usage / Quick Start
11. API Reference (if applicable)
12. Scripts
13. Testing
14. Deployment
15. Contributing
16. License
17. Acknowledgements (if applicable)

📐 Section-by-Section Rules

1. Project Banner / Hero

Use the project name as an <h1> with an emoji that matches the domain
Write a one-line tagline — sharp, no fluff
Include shields.io badges for: build status, license, node version, npm version (use relevant ones only)

Example badge format:

![License](https://img.shields.io/badge/license-MIT-blue.svg)
![Node](https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen)

2. Table of Contents

Auto-linked to every H2 section
Use GitHub anchor format: [Section](#section-name)

3. Overview

2–4 sentences MAX
Answer: what it does, who it's for, why it exists
No marketing fluff — be technical and direct

4. Features

Bullet list, each item starts with a relevant emoji
Each feature is one line — no nested bullets
Max 8 features

5. Tech Stack

Use a markdown table with columns: Technology, Purpose, Version
List only direct dependencies — not transitive ones

6. Project Structure

Use a code block with directory tree
Add inline comments explaining each folder/file's purpose

Example:

src/
├── agent.ts        # Main LLM agent loop
├── client.ts       # MCP client setup
└── tools/
    └── weather.ts  # Weather tool definition

Read the full file on GitHub · 187 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.

2mo ago First seen · 187 lines · 1,421 tokens per session scan A 102d28c8afcb

Subscribe to this mod's changes

mcp-foundry copilot-instructions.md is an instructions file published in the GitHub repository Mahima-Sanketh-Git/mcp-foundry (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,421 tokens to every session, about $0.0057 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.

Writing and docs agentic-ai gemini-ai mcp mcp-client mcp-server mcp-tools

mcp-foundry copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp-foundry copilot-instructions.mdMahima-Sanketh-Git/mcp-foundry	Instructions file	0	5mo ago	MIT	A	1,421	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	3d ago	MIT	A	4,313	Codex, OpenCode

mcp-foundry: Instructions file for GitHub Copilot