A command-line skill for querying Maestro/BAR dependency-flow data from a terminal. Maestro/BAR tracks how changes and builds move through .NET repositories and build pipelines.

Use it for subscription health checks, tracing build flows, checking codeflow status, discovering channels, and triggering subscription updates.

It lets you query this information with shell commands and structured JSON when the matching server tools are unavailable or when you need to script the investigation.

maestro-cli — Skill for Claude Code by ANcpLua/ancplua-claude-plugins

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 maestro-cli

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/maestro-cli/github.svg)](https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/maestro-cli)

Your own site

<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/maestro-cli"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/maestro-cli/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/maestro-cli"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/maestro-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,071 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.00124	$0.01071
Opus 5.5	$0.00050	$0.00428
Sonnet 5.5	$0.00025	$0.00214
Haiku 4.5	$0.00012	$0.00107

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

Security

Grade A, and why

maestro-cli 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.

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/maestro-cli/SKILL.md · 121 lines

How it starts

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

Maestro CLI

Query Maestro/BAR data via the mstro CLI tool instead of loading MCP tools into context. Same data, same caching, zero context tax — agents discover capabilities progressively through --help and mstro guide.

When to Use This Skill

Use this skill when:

You need Maestro/BAR data but the maestro MCP server isn't configured
You're scripting or chaining commands with jq, grep, or other CLI tools
You want structured JSON output for downstream processing
The task is one-shot (not a multi-turn conversational investigation)

Prefer MCP-based skills (flow-analysis, flow-tracing) when:

The maestro MCP server is already loaded in your tool list
You're doing multi-turn conversational investigation
You need markdown-formatted output with visual indicators

Installation

dotnet tool install -g lewing.maestro.mcp

After installation, mstro is available globally. Verify: mstro --help

Note: The same package (lewing.maestro.mcp) serves as both a .NET global tool (providing the mstro CLI) and an MCP server (via dotnet dnx). The CLI is what this skill uses.

Authentication

Three-tier cascade (automatic fallback):

MAESTRO_BAR_TOKEN env var — explicit PAT
Cached Entra ID — reuses darc authenticate credentials from ~/.darc/.auth-record-*
Anonymous — read-only fallback (may be rate-limited)

Run darc authenticate once for persistent credentials.

Progressive Discovery

Don't memorize commands. Discover them:

mstro --help              # All commands, one line each
mstro <command> --help    # Parameters for a specific command
mstro <command> --schema  # JSON response field names (for jq pipelines)
mstro guide               # Workflow-organized guide (~3KB)

Before writing jq queries, run --schema to see the response shape:

mstro subscription-health --schema   # → shows StaleSubs[].Id, .BuildsBehind, etc.
mstro latest-build --schema          # → shows Id, Repository, Commit, etc.

Read the full file on GitHub · 121 lines

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 · 121 lines · 124 tokens per session scan A a63e4de7475a

Subscribe to this mod's changes

maestro-cli is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 1,071 once invoked, about $0.0005 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.

CI and CD DevOps and cloud ancplua-fleet

maestro-cli next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
maestro-cliANcpLua/ancplua-claude-plugins	Skill	6	2d ago	MIT	A	124	Claude Code
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	yesterday	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	today	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.2k	3d ago	MIT	A	56	Claude Code, Codex
deployment-engineerrmyndharis/antigravity-skills	Skill	2.0k	4d ago	MIT	A	73	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	2d ago	MIT	C	54	Claude Code
managing-github-actions-secretsPostHog/posthog-foss	Skill	730	today	MIT	A	67	Claude Code, Codex