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.
npx agentmods add skills/ancplua/ancplua-claude-plugins/maestro-clinpx skills add ANcpLua/ancplua-claude-plugins --skill maestro-cligit clone --depth 1 https://github.com/ANcpLua/ancplua-claude-pluginsWrote 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/skills/ancplua/ancplua-claude-plugins/maestro-cli)<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="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.00124 | $0.01071 |
| Opus 5 | $0.00062 | $0.00535 |
| Sonnet 5 | $0.00025 | $0.00214 |
| Haiku 4.5 | $0.00012 | $0.00107 |
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 6d 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 — 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 themstroCLI) and an MCP server (viadotnet dnx). The CLI is what this skill uses.
Authentication
Three-tier cascade (automatic fallback):
MAESTRO_BAR_TOKENenv var — explicit PAT- Cached Entra ID — reuses
darc authenticatecredentials 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.
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.
- 6d ago First seen · 121 lines · 124 tokens per session scan A a63e4de7475a
maestro-cli is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (5 stars, last pushed 19d ago), licensed MIT. It adds 124 tokens to every session and 1,071 once invoked, about $0.0006 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-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.