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/microsoft/bc-bench/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/BC-BenchWhat 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.00879 | $0.00879 |
| Opus 5 | $0.00439 | $0.00439 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
BC-Bench 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository: microsoft/BC-Bench
This is a benchmark for evaluating coding agents on real-world Business Central (AL) development tasks, inspired by SWE-Bench. Unlike traditional model benchmarks, BC-Bench is designed to help select models and rapidly iterate on mcp servers, custom instruction/agents, etc for engineers. The repository contains:
- Dataset: Benchmark entries following SWE-Bench schema with BC-specific adjustments
- Python Package (
src/bcbench/): CLI tools, agent implementations, and validation utilities - PowerShell Scripts (
scripts/): Environment setup and dataset verification using AL-GO/BCContainerHelper - Tools (
tools/): Ad-hoc scripts for GitHub Artifacts download, etc - Agent Evaluations: Focuses on GitHub Copilot CLI and Claude Code
- Experiments: MCP Servers, custom instructions, custom agents, skills, etc. and their performance on the benchmark
- Notebooks (
notebooks/): Analysis and visualization of benchmark results
Key Context
- Primary language: Python (with AL/Business Central as the target evaluation language)
- Uses
uvfor dependency management: e.g.uv add <package>to add packages,uv run <command>to run commands - Uses
pre-commitfor code quality checks (ruff linting/formatting, trailing whitespace, etc.)
Categories
BC-Bench is category-based and designed to grow over time. It currently has two categories, bug-fix and test-generation. They share the same dataset tasks and execution-based setup, but use different prompts, expected outputs, and evaluation pipelines. Future categories such as code-review can be added within the same overall benchmark structure, though they may require different inputs, setup, or evaluation methods.
Coding Patterns and Guidelines
- Prefer strong typing and type hints
- Prefer simple code for fast iteration
- Prefer modular, testable components
- Prefer pure functions where possible
- Prefer explicit over implicit
- Prefer high-order functions like map, filter, reduce over loops
- Prefer immutable data structures where possible
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 · 66 lines · 879 tokens per session scan A 6a7e82c11e64
BC-Bench copilot-instructions.md is an instructions file published in the GitHub repository microsoft/BC-Bench (56 stars, last pushed 4d ago), licensed MIT. It adds 879 tokens to every session, about $0.0044 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
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).
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.
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.
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 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).
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.