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 skills add michele-prandina/ClaudE2E --skill maestrogit clone --depth 1 https://github.com/michele-prandina/ClaudE2EWrote 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/michele-prandina/claude2e/maestro)<a href="https://agentmods.dev/skills/michele-prandina/claude2e/maestro"><img src="https://agentmods.dev/badge/skills/michele-prandina/claude2e/maestro/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.
<a href="https://agentmods.dev/skills/michele-prandina/claude2e/maestro"><img src="https://agentmods.dev/badge/skills/michele-prandina/claude2e/maestro.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00937 |
| Opus 5 | $0.00006 | $0.00468 |
| Sonnet 5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
maestro 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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 12d ago First seen · 125 lines · 13 tokens per session scan A 37c347c592f2
maestro is a skill published in the GitHub repository michele-prandina/ClaudE2E (8 stars, last pushed 6mo ago), with no licence file. It adds 13 tokens to every session and 937 once invoked, about $0.0001 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
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
e2e-patterns
Write robust E2E tests with Playwright — page objects, resilient waiting, auth, and CI integration.
test-pyramid
Decide what type of test to write, structure the suite, measure health, and apply test doubles correctly.
mobile-testing
When writing E2E tests for mobile or configuring Detox.
blackbox-testing
Automates end-to-end and system validation tests. Runs services via Docker, feeds inputs, executes scenarios, and verifies outputs.
before-after
Prove a UI change worked by capturing the page before the edit and again after it with identical capture parameters, then reporting a concrete diff. Use when the user asks you to verify, confirm or show that a fix landed, wants a before/after comparison, or doubts that a change had any effect.