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/mahima-sanketh-git/mcp-foundry/copilot-instructionsgit clone --depth 1 https://github.com/Mahima-Sanketh-Git/mcp-foundryWrote 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/mahima-sanketh-git/mcp-foundry/copilot-instructions)<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="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.01421 | $0.01421 |
| Opus 5 | $0.00711 | $0.00711 |
| Sonnet 5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
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 4d 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 — 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:
 
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
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.
- 4d ago First seen · 187 lines · 1,421 tokens per session scan A 102d28c8afcb
mcp-foundry copilot-instructions.md is an instructions file published in the GitHub repository Mahima-Sanketh-Git/mcp-foundry (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,421 tokens to every session, about $0.0071 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
director CLAUDE.md
Claude Code instructions for fdmtl/director, covering claude.md, product overview and development workflow, quality standards and workflow, engineering excellence and library documentation lookup.
Genesis-World-MCP AGENTS.md
AGENTS.md instructions for Gnidreve/Genesis-World-MCP, covering agents.md — cas genesisworld mcp, what this is, standing orders — read first, design pillars and source layout & conventions.
pixabay-mcp-server CLAUDE.md
Claude Code instructions for hanoak/pixabay-mcp-server, covering claude.md, project overview, tech stack (decided — do not relitigate without discussion), architecture & folder conventions and coding standards.
reporelay AGENTS.md
Instructions for chwoerz/reporelay, covering agents.md — reporelay, build / dev / test commands, running a single test, database & codegen and project structure.
atelier-mcp copilot-instructions.md
Copilot instructions for anshrajore/atelier-mcp, covering run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
md-vision-mcp AGENTS.md
AGENTS.md instructions for japlete/md-vision-mcp, covering md vision mcp server, status, layout, stack and rules.