Borrowing it
Nothing to install: this file belongs to jrmatherly/mcp-context-forge. 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/jrmatherly/mcp-context-forge/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/jrmatherly/mcp-context-forgeWrote 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/jrmatherly/mcp-context-forge/copilot-instructions)<a href="https://agentmods.dev/instructions/jrmatherly/mcp-context-forge/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jrmatherly/mcp-context-forge/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.1 | $0.00789 | $0.00789 |
| Opus 5 | $0.00394 | $0.00394 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
mcp-context-forge 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD Method — Project Instructions
Project Configuration
- Project: mcp-context-forge
- User: Jason
- Communication Language: English
- Document Output Language: English
- User Skill Level: intermediate
- Output Folder: {project-root}/_bmad-output
- Planning Artifacts: {project-root}/_bmad-output/planning-artifacts
- Implementation Artifacts: {project-root}/_bmad-output/implementation-artifacts
- Project Knowledge: {project-root}/docs
BMAD Runtime Structure
- Agent definitions:
_bmad/bmm/agents/(BMM module) and_bmad/core/agents/(core) - Workflow definitions:
_bmad/bmm/workflows/(organized by phase) - Core tasks:
_bmad/core/tasks/(help, editorial review, indexing, sharding, adversarial review) - Core workflows:
_bmad/core/workflows/(brainstorming, party-mode, advanced-elicitation) - Workflow engine:
_bmad/core/tasks/workflow.xml(executes YAML-based workflows) - Module configuration:
_bmad/bmm/config.yaml - Core configuration:
_bmad/core/config.yaml - Agent manifest:
_bmad/_config/agent-manifest.csv - Workflow manifest:
_bmad/_config/workflow-manifest.csv - Help manifest:
_bmad/_config/bmad-help.csv - Agent memory:
_bmad/_memory/
Key Conventions
- Always load
_bmad/bmm/config.yamlbefore any agent activation or workflow execution - Store all config fields as session variables:
{user_name},{communication_language},{output_folder},{planning_artifacts},{implementation_artifacts},{project_knowledge} - MD-based workflows execute directly — load and follow the
.mdfile - YAML-based workflows require the workflow engine — load
workflow.xmlfirst, then pass the.yamlconfig - Follow step-based workflow execution: load steps JIT, never multiple at once
- Save outputs after EACH step when using the workflow engine
- The
{project-root}variable resolves to the workspace root at runtime
Available Agents
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 · 59 lines · 789 tokens per session scan A 5ac47cadf263
mcp-context-forge copilot-instructions.md is an instructions file published in the GitHub repository jrmatherly/mcp-context-forge (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 789 tokens to every session, about $0.0039 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-09-03.
Other instructions, from other repositories
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.
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.
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).
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).
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.
spec-kit AGENTS.md
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.