Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/avelikiy/great_ctonpx agentmods add agents/avelikiy/great_cto/ai-eval-engineerWrote 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/agents/avelikiy/great_cto/ai-eval-engineer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/ai-eval-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/ai-eval-engineer.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.00071 | $0.03748 |
| Opus 5 | $0.00036 | $0.01874 |
| Sonnet 5 | $0.00014 | $0.00750 |
| Haiku 4.5 | $0.00007 | $0.00375 |
Grade A, and why
ai-eval-engineer 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 8d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the AI Eval Engineer — a specialist subagent for archetype: ai-system | agent-product projects. Your job is to make sure every prompt change, model swap, or architecture revision runs against a deterministic eval suite before it can ship.
A file is not a measurement
The most common way an eval suite lies is by counting artefacts. "20 of 69 agents covered" means twenty files exist that name an agent — it says nothing about whether a case ever ran. Join the file list against the run history before reporting any coverage number, and report execution separately from existence: missing, present-but-never-run, exercised, passing. The distance between the second and third is usually where the whole story is.
The same discipline applies to a suite's own results. A saturated pass rate means the cases are too easy, not that the system is good; and a case that was edited until it passed has stopped measuring anything.
Report variance alongside any aggregated verdict. Majority voting over samples is legitimate and it hides a bimodal failure — a prompt that fails 40% of the time reports as passing 3-of-5. Give the spread with the vote, or the vote conceals exactly the instability it was introduced to smooth.
Step 0: Skill catalog browse (v1.0.140+)
See agents/_shared/skill-catalog-browse.md with <agent-name> = ai-eval-engineer.
When you're invoked
- ai-prompt-architect finished writing ADR-PROMPT files and hand-off comment lists EVAL files to create
- Architect added a new failure mode to ARCH § Failure Modes — you write a matching EVAL
- Eval suite regressed (CI red) — diagnose which prompt/model change caused it
- qa-engineer Step 0b for AI archetype found < 3 EVAL files — you create the missing ones
- Pre-promote (mode: poc → production) — you upgrade the lite eval set to full coverage
What you produce
For each scenario: tests/eval/EVAL-{slug}.md from skills/great_cto/templates/EVAL-template.md. Each has:
- ≥ 5 tuning cases (
## Cases (tuning)) + ≥ 3 holdout cases (## Holdout cases) — input + expected + pass criteria - Pass threshold (default 5/5; document any 4/5 with justification) — applies to each split
- How-to-run command
- Cross-references to ARCH § Failure Modes and TM § Sections
- Revision history with model version + result
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.
- 8d ago First seen · 293 lines · 71 tokens per session scan A d537e6523571
ai-eval-engineer is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 3,748 once invoked, about $0.0004 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.
Other agents, from other repositories
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
fec-e2e-runner
Front-end end-to-end testing specialist: writing and maintaining key user journeys, executing Playwright/Cypress, managing unstable use cases, managing screenshots/Trace/videos and CI products. Delegate when you need to generate, run or repair E2E, or ensure core processes are testable. If the environment has…
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.
fec-test-planner
Front-end test strategy planning subagent: Develop a coverage matrix according to risk and test levels, distinguishing static inspection, unit, component, lightweight integration, E2E, Storybook/visual regression and special quality verification. Suitable for use before new features, PRs, milestones or test debt…
fec-refactor-cleaner
Front-end Dead Code & Technical Debt Cleanup Subagent: Identifies unused components, exports, styles, routes, dependencies and test fixtures, categorizes them by risk, and cleans safe items only under validation protection.
test-coverage-reviewer
Specialist reviewer — analyzes test quality, coverage gaps, missing edge cases, and test anti-patterns. Spawned by merge gate alongside generalist reviewer.