vizro-e2e-flow

A workflow for building Vizro dashboards, which are interactive screens for exploring data through charts and controls. It covers requirements, layout, chart selection, Python implementation, deployment, and testing.

In plain words
What is it for?
Use it to plan a dashboard, choose visualizations, build it in Python, test it, and prepare it for deployment.
Why use it?
It gives a project a structured path from an idea to a tested, deployed dashboard.

Plugin for Claude Code

Install

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.

agentmods
npx agentmods add plugins/mckinsey/vizro/vizro-e2e-flow
Claude Code
/plugin marketplace add mckinsey/vizro
Clone the repo
git clone --depth 1 https://github.com/mckinsey/vizro

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

vizro-e2e-flow 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 yesterday.

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.

vizro-e2e-flow/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "vizro-e2e-flow",
  "version": "0.1.7",
  "description": "Build Vizro dashboards from concept to deployment. Enforces a 2-phase workflow covering requirements, layout design, visualization selection, implementation with Python, and testing.",
  "author": {
    "name": "Vizro Team",
    "email": "[email protected]"
  },
  "homepage": "https://vizro.readthedocs.io",
  "repository": "https://github.com/mckinsey/vizro/vizro-e2e-flow"
}
Changes

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.

  1. yesterday First seen · 12 lines scan A ffc898f2c30b

Subscribe to this mod's changes

vizro-e2e-flow is a plugin published in the GitHub repository mckinsey/vizro (3,787 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.