evaluate

A workflow review tool that tests an AI workflow against realistic situations. It checks whether tasks finish, outputs are correct, errors are handled usefully, and interactions are suitable for users.

In plain words
What is it for?
Use it for quality reviews, interaction audits, scenario testing, edge-case checks, and regression testing.
Why use it?
It helps reveal failures that may not appear when testing only the normal successful path.

Skill for Claude CodeCodex

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 skills/sharpdeveye/maestro/evaluate
Any agent
npx skills add sharpdeveye/maestro --skill evaluate
Clone the repo
git clone --depth 1 https://github.com/sharpdeveye/maestro

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 651 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00651
Opus 5 $0.00012 $0.00326
Sonnet 5 $0.00005 $0.00130
Haiku 4.5 $0.00002 $0.00065

Measured yesterday against content hash 7f3cb4e8eee3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

source/skills/evaluate/SKILL.md · 92 lines

How it starts

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

MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first. Consult the feedback-loops reference in the agent-workflow skill for evaluation patterns, golden test sets, and regression detection.


Evaluate the workflow's actual interaction quality by testing it against scenarios that represent real usage.

Evaluation Dimensions

1. Task Completion

  • Does the workflow actually accomplish what it's supposed to?
  • Does it handle the complete task or only the happy path?
  • Are edge cases addressed or silently dropped?

2. Output Quality

  • Is the output accurate, complete, and well-formatted?
  • Does it match the defined output schema (if any)?
  • Would a domain expert approve the output?

3. Error Behavior

  • What happens when input is malformed?
  • What happens when a tool fails?
  • What happens when the model is uncertain?
  • Is the error message useful or generic?

4. User Experience

  • Is the interaction natural and intuitive?
  • Are confirmations requested for destructive operations?
  • Is the response time acceptable?
  • Does the workflow communicate its limitations?

5. Consistency

  • Does the same input produce consistent output quality?
  • Are there random failures that aren't reproducible?
  • Does quality degrade over long conversations?

Scenario Testing

Create and run test scenarios:

Scenario Input Expected Actual Grade
Happy path Normal input Correct output ? A-F
Edge case Unusual input Graceful handling ? A-F
Error case Bad input Helpful error ? A-F
Stress case Large/complex input Reasonable handling ? A-F
Adversarial Tricky/malicious input Safe response ? A-F

Evaluation Report

Produce a structured report with:

  1. Overall quality grade (A-F)
  2. Per-dimension scores with evidence
  3. Specific scenario results
  4. Priority improvements with recommended Maestro commands

Read the full file on GitHub · 92 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.

  1. yesterday First seen · 92 lines · 23 tokens per session scan A 7f3cb4e8eee3

Subscribe to this mod's changes

evaluate is a skill published in the GitHub repository sharpdeveye/maestro (415 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 651 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-30.

Related

Other skills, from other repositories

agent-self-scheduling

Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.

sickn33/agentic-awesome-skills · 24 tokens

research

Research and information retrieval capability powered by LangChain.js. Uses GPT-4o to answer questions, summarize information, provide detailed analysis, and generate structured research outputs.

GetBindu/Bindu · 1 tokens

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

agnt-gg/agnt · 64 tokens

agnt-plugin-builder

End-to-end workflow for creating, building, installing, and hot-reloading AGNT plugins entirely from chat. Use this skill whenever the user asks to 'build a plugin', 'create an AGNT plugin', 'add a new tool to AGNT', 'integrate X with AGNT' (where X is an API or service), 'make a plugin for [service]', or wants to…

agnt-gg/agnt · 201 tokens

annie-universal-api-orchestrator

Use AGNT's stored OAuth tokens and API keys to call ANY third-party API directly from the orchestrator, without building a tool or plugin first. Use this skill whenever the user asks you to "do something with my GitHub / Gmail / Drive / Slack / Notion / Stripe / Shopify / Discord / Linear / Jira / Vercel / Netlify /…

agnt-gg/agnt · 208 tokens

frontend-slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

agnt-gg/agnt · 63 tokens