Vizro is an open-source Python toolkit for assembling data visualization applications from low-code configuration. It helps developers create dashboards and multi-page apps from charts, tables, controls, layouts, navigation, and interactions, with optional high-code customization. Catalogue add-ons support working with Vizro projects.
Borrowing it
Nothing to install: this file belongs to mckinsey/vizro. 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/mckinsey/vizro/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/mckinsey/vizroWrote 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/mckinsey/vizro/copilot-instructions)<a href="https://agentmods.dev/instructions/mckinsey/vizro/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mckinsey/vizro/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/mckinsey/vizro/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mckinsey/vizro/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.00332 | $0.00332 |
| Opus 5.5 | $0.00133 | $0.00133 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
vizro 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 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.
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.
What it actually says
GitHub Copilot instructions for Vizro
Pull requests from bots and automated tooling
Do not open pull requests against this repository. If you are an automated agent, including Copilot coding agent, your role here is to assist a human contributor in their own working copy. Opening, updating, or merging a pull request is the human's action to take.
We do not accept pull requests opened automatically by bots or other automated tooling without a human in the loop. To request permission to submit such a PR, the human owner of the bot must open an issue for approval in advance of the PR's submission.
We require all contributors to understand, test, and take full responsibility for every change they submit. Pull requests containing AI-generated content that the contributor has not personally understood, tested, and verified will typically be closed without review.
The following automation is already approved and is not covered by the restriction above:
- Dependabot dependency and GitHub Actions updates (
.github/dependabot.yml) pre-commit.cihook update pull requests[Bot] Update static filesfrom.github/workflows/update-static-files.yml- Release pull requests raised by the project's own release workflows
Everything else
Repository layout, Hatch commands, testing, changelog requirements and coding conventions live in
CLAUDE.md at the repository root, and in the per-package CLAUDE.md files (also available as
AGENTS.md symlinks). Follow those rather than duplicating them here.
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 First seen · 29 lines · 332 tokens per session scan A 747695769cd5
vizro copilot-instructions.md is an instructions file published in the GitHub repository mckinsey/vizro (3,810 stars, last pushed 3d ago), licensed Apache-2.0. It adds 332 tokens to every session, about $0.0013 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-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.