A pack of slash commands and sub-agents for Claude Code and Cursor that turns “I think the agent works” into an eval suite, a trace review, a regression check, and a red-team pass — run from inside the editor you already use.
The problem
Testing an AI agent is not like testing a function. There is no single correct output, the failure modes are fuzzy, and every prompt change silently rewrites behaviour you already verified. Most teams end up eyeballing a handful of runs and calling it done — then find out in production that a model update broke a path nobody thought to check.
This toolkit gives that work a shape: written evals, a repeatable trace review, a regression check you run after every prompt or model change, and an adversarial pass to find the inputs you would not have thought of.
What's inside
.mdc rules, so the pack works in either editor.How it runs
# drop the pack into your project
.claude/commands/ → 4 slash commands
.claude/agents/ → 3 sub-agents
.cursor/rules/ → same workflows for Cursor
# then, in Claude Code:
/eval-suite examples/example-agent-spec.md
/trace-review
/regression-check
Plain markdown and frontmatter. Nothing to install, no server to run, no account to create, no telemetry.
Fit
You are building an agent or an LLM feature in Claude Code or Cursor, you change prompts or swap models often, and you want the QA step to be a command you run rather than a discipline you keep forgetting.
You need a hosted eval platform with dashboards, team seats, and stored run history — this is a local pack of prompts, deliberately. It also won't help much if your agent has no spec at all; write one first.
Details
One-time $29. Download instantly, keep the files, use them in as many of your own projects as you like.
AI-assisted, human-reviewed: every file was written and read line by line before release.