eval

eval is a skill for Claude Code, Codex from ai-analyst-lab/ai-analyst-plus. It costs 134 tokens per session (1,796 once invoked), scanned A, original, MIT.

A skill that runs a live evaluation suite: a set of test questions with hidden reference answers. It measures answer accuracy, query similarity, cost, and response time.

In plain words
What is it for?
Use it to run the train, test, or full evaluation split, optionally limiting the run to the first few cases.
Why use it?
It shows whether an analyst system works on known cases and helps detect regressions. The test answers stay hidden until grading.

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/ai-analyst-lab/ai-analyst-plus/eval
Any agent
npx skills add ai-analyst-lab/ai-analyst-plus --skill eval
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-plus

Made for: Claude Code, Codex.

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

agentmods badge for eval

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plus/eval.svg)](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst-plus/eval)
Your own site
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst-plus/eval"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plus/eval.svg" alt="Measured on agentmods" height="20"></a>
Per session 134 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,796 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.00134 $0.01796
Opus 5 $0.00067 $0.00898
Sonnet 5 $0.00027 $0.00359
Haiku 4.5 $0.00013 $0.00180

Measured 5d ago against content hash cd88acbb363b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

eval 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 5d 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.

.claude/skills/eval/SKILL.md · 117 lines

How it starts

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

Skill: Eval (live gold-suite runner)

Purpose

Run the analyst on every question in the held-out gold suite, then score the answers against the blind gold: accuracy (the analyst's number vs the recomputed gold), query-similarity (its SQL vs the approved query), and cost/latency. This is the system-level eval — the climb the Context pillar moves and the number the model comparison turns on.

Two honest properties:

  • Blind by construction. The analyst runs see the question only — never the gold sql or value. The gold is read only at grading, after the answers are locked.
  • Real, not staged. Each answer is produced by actually running the analyst now. Nothing is pre-filled.

Invocation

/eval [train|test|all] [--slice N] — default split train.

  • train — the working set you iterate on (error-analyze, add context, watch it climb). Default.
  • test — the held-out set. Run this ONCE at the end as the honest generalization number. Never iterate against it (D8).
  • --slice N — run only the first N cases (the in-room live slice). Omit for the full split.

Examples: /eval train · /eval train --slice 3 · /eval test

How to run it

Step 0 — preflight (D3, fail loud)

from helpers.eval_driver import preflight
conn = preflight()   # raises clearly if Snowflake isn't live — there is NO DuckDB fallback

If it raises, stop and surface the message. Do not grade against any other engine.

Step 1 — get the questions (blind)

Load the question set for the split. This returns questions only — no answers — so you cannot leak the key:

import sys; sys.path.insert(0, "<ai-analytics-evals path>")
from aievals.data.gold import load_questions
questions = load_questions("<...>/aievals/data/novamart_gold.yaml", split="train")  # [{question, split}]

If --slice N was given, take the first N.

Step 2 — run the analyst once per question

Launch one fresh sub-agent per question with the Task/Agent tool (run them concurrently in reasonable batches). Each sub-agent gets a fresh context and sees ONLY its question. Time each run (wall-clock) for latency. Give each sub-agent exactly this brief:

Read the full file on GitHub · 117 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. 5d ago First seen · 117 lines · 134 tokens per session scan A cd88acbb363b

Subscribe to this mod's changes

eval is a skill published in the GitHub repository ai-analyst-lab/ai-analyst-plus (19 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 1,796 once invoked, about $0.0007 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens