evaluating-llms

evaluating-llms is a skill for Claude Code from ancoleman/ai-design-components. It costs 50 tokens per session (4,422 once invoked), scanned A, original, MIT.

A guide for testing large language model systems, including tools that generate text and systems that retrieve documents before answering. It covers automated checks, model comparisons, and safety measurements.

In plain words
What is it for?
Use it to test prompts, validate document-retrieval pipelines, measure hallucinations or toxicity, compare models, run benchmarks, and add quality checks to deployment pipelines.
Why use it?
It helps reveal incorrect answers, made-up information, bias, harmful content, or quality differences before an AI system reaches users.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/run_ragas_eval.py --dataset data/qa_dataset.json --output results.json.

Part of the ai-ml-skills plugin — 4 skills shipped together

Good fit Use it to test prompts, validate document-retrieval pipelines, measure hallucinations or toxicity, compare models, run benchmarks, and add quality checks to deployment pipelines.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ancoleman/ai-design-components
agentmods
npx agentmods add skills/ancoleman/ai-design-components/evaluating-llms

Made for: Claude Code.

Or install ai-ml-skills, the plugin that ships this one along with the rest of its 4 skills.

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 evaluating-llms

README.md
[![agentmods](https://agentmods.dev/badge/skills/ancoleman/ai-design-components/evaluating-llms/github.svg)](https://agentmods.dev/skills/ancoleman/ai-design-components/evaluating-llms)
Your own site
<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/evaluating-llms"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/evaluating-llms/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.

agentmods 80×15 button for evaluating-llms

Your own site · 80×15
<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/evaluating-llms"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/evaluating-llms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,422 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00050 $0.04422
Opus 5.5 $0.00020 $0.01769
Sonnet 5.5 $0.00010 $0.00884
Haiku 4.5 $0.00005 $0.00442

Measured 1mo ago against content hash 55f8ebd7adde, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

evaluating-llms 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 1mo ago.

The scan reads SKILL.md. This mod also ships 9 executable files (examples/python/benchmark_testing.py, examples/python/classification_metrics.py, examples/python/deepeval_example.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/evaluating-llms/SKILL.md · 486 lines

How it starts

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

LLM Evaluation

Evaluate Large Language Model (LLM) systems using automated metrics, LLM-as-judge patterns, and standardized benchmarks to ensure production quality and safety.

When to Use This Skill

Apply this skill when:

  • Testing individual prompts for correctness and formatting
  • Validating RAG (Retrieval-Augmented Generation) pipeline quality
  • Measuring hallucinations, bias, or toxicity in LLM outputs
  • Comparing different models or prompt configurations (A/B testing)
  • Running benchmark tests (MMLU, HumanEval) to assess model capabilities
  • Setting up production monitoring for LLM applications
  • Integrating LLM quality checks into CI/CD pipelines

Common triggers:

  • "How do I test if my RAG system is working correctly?"
  • "How can I measure hallucinations in LLM outputs?"
  • "What metrics should I use to evaluate generation quality?"
  • "How do I compare GPT-4 vs Claude for my use case?"
  • "How do I detect bias in LLM responses?"

Evaluation Strategy Selection

Decision Framework: Which Evaluation Approach?

By Task Type:

Task Type Primary Approach Metrics Tools
Classification (sentiment, intent) Automated metrics Accuracy, Precision, Recall, F1 scikit-learn
Generation (summaries, creative text) LLM-as-judge + automated BLEU, ROUGE, BERTScore, Quality rubric GPT-4/Claude for judging
Question Answering Exact match + semantic similarity EM, F1, Cosine similarity Custom evaluators
RAG Systems RAGAS framework Faithfulness, Answer/Context relevance RAGAS library
Code Generation Unit tests + execution Pass@K, Test pass rate HumanEval, pytest
Multi-step Agents Task completion + tool accuracy Success rate, Efficiency Custom evaluators

By Volume and Cost:

Samples Speed Cost Recommended Approach
1,000+ Immediate $0 Automated metrics (regex, JSON validation)
100-1,000 Minutes $0.01-0.10 each LLM-as-judge (GPT-4, Claude)
< 100 Hours $1-10 each Human evaluation (pairwise comparison)

Read the full file on GitHub · 486 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. 1mo ago First seen · 486 lines · 50 tokens per session scan A 55f8ebd7adde

Subscribe to this mod's changes

evaluating-llms is a skill published in the GitHub repository ancoleman/ai-design-components (524 stars, last pushed 10mo ago), licensed MIT. It adds 50 tokens to every session and 4,422 once invoked, about $0.0002 per session on Opus 5.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

seo-aeo-geo

Optimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure…

rampstackco/claude-skills · 163 tokens

jev-integrate

Wire a System One model (Jev, or an open reproduction like Von) into a product feature — routing, guardrails, scoring, classification. Use when replacing an LLM call that returns a label rather than prose, when adding a typed decision to an agent loop, or when deciding between the hosted Jev API and a local open…

OneWave-AI/claude-skills · 98 tokens

jev-eval

Build and run a labelled eval set for a System One model (Jev, Von, or any typed-decision config), then sweep criteria wordings and thresholds against it. Use when a Jev/Von classification is wrong or unreliable, when choosing between the hosted API and a local open model, when tuning noul thresholds, or before…

OneWave-AI/claude-skills · 92 tokens

jev-audit

Audit a codebase for LLM calls that are really classifications in disguise, then produce a costed swap plan for a System One model. Use when asked to cut AI inference cost or latency, when scoping a performance engagement for a client, when reviewing an agent loop that feels slow, or when asked "where could we use Jev…

OneWave-AI/claude-skills · 89 tokens

automl-hyperparameter-optimization

Best practices for AutoML and hyperparameter search with Optuna, Ray Tune, and PyCaret, covering search-space design, validation splits, and leakage prevention. Use when tuning model hyperparameters, setting up a pruned or distributed hyperparameter search, designing a nested validation scheme, or evaluating whether…

Mindrally/skills · 76 tokens

google-adk

Best practices for building AI agents with Google's Agent Development Kit (ADK) in Python, covering agent design, tools, sessions, memory, artifacts, evaluation, and deployment. Use when building LLM agents or multi-agent systems with ADK, defining ADK tools, wiring up sessions/state/memory, working with ADK…

Mindrally/skills · 90 tokens