What is flow-analysis?

A diagnostic guide for VMR codeflow, the process that moves code changes between related .NET repositories. It uses scripts and connected tools to inspect pull requests, builds, subscriptions, and dependencies.

Use it to investigate one codeflow pull request, check whether a fix has passed through the VMR pipeline, or review flow health across a repository.

It helps explain why a code change has not reached another repository, why a pull request is stale, or why an automated backflow pull request is missing or blocked.

flow-analysis — Skill for Claude Code by ANcpLua

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.

Any agent

npx skills add ANcpLua/ancplua-claude-plugins --skill flow-analysis

Clone the repo

git clone --depth 1 https://github.com/ANcpLua/ancplua-claude-plugins

Made for: Claude Code.

Or install dotnet-dnceng, the plugin that ships this one along with the rest of its 10 skills, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/flow-analysis/github.svg)](https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/flow-analysis)

Your own site

<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/flow-analysis"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/flow-analysis/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/flow-analysis"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/flow-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 152 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,213 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00152	$0.05213
Opus 5.5	$0.00061	$0.02085
Sonnet 5.5	$0.00030	$0.01043
Haiku 4.5	$0.00015	$0.00521

Measured 2mo ago against content hash 3a20527c4245, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flow-analysis 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 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/Get-CodeflowStatus.ps1, scripts/Get-FlowHealth.ps1), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/dotnet-dnceng/skills/flow-analysis/SKILL.md · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flow Analysis

Analyze VMR codeflow PR health using scripts for data collection and MCP tools for enrichment and remediation. For single-PR analysis, Get-CodeflowStatus.ps1 does comprehensive data collection (VMR commit comparison, forward flow discovery, staleness detection); maestro MCP tools provide subscription triggering and build freshness. For repo-wide flow health, flow-health.cs handles batch GitHub scanning in parallel.

🚨 NEVER use gh pr review --approve or --request-changes. Only --comment is allowed.

When to Use This Skill

Use this skill when:

A codeflow PR (from dotnet-maestro[bot]) is stale or failing and you need to understand why
You need to check if a specific fix has flowed through the VMR pipeline
A PR has a Maestro staleness warning or conflict
You want to check overall flow health for a repo ("what's the flow status for the sdk?")
You need to diagnose why backflow PRs are missing or blocked
You're asked "is this codeflow PR up to date", "why is the codeflow blocked", "what's the flow status for net11"

Prerequisites

Maestro MCP server — provides subscription health, build freshness, and codeflow management. See lewing/maestro.mcp for setup.
GitHub CLI (gh) — must be installed and authenticated. Required by flow-health.cs.

Quick Start

For "is the backflow healthy for repo X on branch Y?" — use PR Analysis (Get-CodeflowStatus.ps1 -Repository -Branch). The script finds the open backflow PR (if any), compares VMR commits, discovers forward flow, and extracts warnings — all in one call.

For "what's the flow status across all repos?" or multi-repo/multi-branch scanning — use the Codeflow Overview (MCP tools for subscription health + build freshness across many repos simultaneously).

For investigating a specific PR — use PR Analysis (Get-CodeflowStatus.ps1 -PRNumber). If no open PR exists, the script reports this; use MCP tools to check the subscription state.

Read the full file on GitHub · 322 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 322 lines · 152 tokens per session scan A 3a20527c4245

Subscribe to this mod's changes

flow-analysis is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 152 tokens to every session and 5,213 once invoked, about $0.0006 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-31.

Debugging ancplua-fleet

flow-analysis next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
flow-analysisANcpLua/ancplua-claude-plugins	Skill	6	2d ago	MIT	A	152	Claude Code
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	yesterday	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	today	MIT	A	71	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	2.0k	4d ago	MIT	A	36	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	324	yesterday	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
diagnosing-missing-recordingsPostHog/posthog	Skill	41k	today	none	A	76	Claude Code, Codex