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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/mckinsey/vizro/claude-md"><img src="https://agentmods.dev/badge/instructions/mckinsey/vizro/claude-md.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.00496 | $0.00496 |
| Opus 5 | $0.00248 | $0.00248 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
vizro CLAUDE.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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vizro Development Guide for AI Agents
This is a monorepo containing multiple Vizro packages. The main packages are:
vizro-core/: The core Vizro dashboard frameworkvizro-ai/: Framework for AI-assisted dashboard developmentvizro-mcp/: Model Context Protocol server for AI-assisted dashboard developmentvizro-dash-components/: Custom Dash components maintained by Vizro (TypeScript/React → Python).vizro-e2e-flow/: (Anthropic) Claude Code plugin with skills for end-to-end dashboard development (nohatchcommands)vizro-experimental/: The incubation home for Vizro features that aren't ready forvizro-core. APIs in this package may change or be removed between releases. Once a feature is ready, it graduates tovizro-core.
Development Setup (across all packages)
Only Dependency: Hatch
Vizro uses Hatch as its only direct development dependency. You don't need to manually install Python or create virtual environments - Hatch handles this automatically. If not installed, guide the user on how to install it.
Working Directory
Navigate to the specific package directory (e.g., cd vizro-core) before running Hatch commands.
Common Hatch Commands across all packages
Run these from within the package directory (e.g., vizro-core/):
hatch run python -c "xxx"- Run a Python commandhatch run pypath- Show Python interpreter pathhatch run lint- Check and fix code quality/formattinghatch run changelog:add- Generate changelog fragment (required for PRs)hatch run test-unit- Run test suitehatch run docs:serve- Build and serve documentation (hot-reloads)
Development Flow
- Make changes to code
- Run
hatch run lintto check formatting - Run
hatch run test-unitto verify tests pass (you can add --last-failed to rerun only failures from the last test run) - Run
hatch run changelog:addto create changelog fragment
Key configuration files
pyproject.toml: Main tooling configuration for the monorepo
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.
- 8d ago First seen · 45 lines · 496 tokens per session scan A cb1c3acd5427
vizro CLAUDE.md is an instructions file published in the GitHub repository mckinsey/vizro (3,789 stars, last pushed today), licensed Apache-2.0. It adds 496 tokens to every session, about $0.0025 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
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.