eval-engineering

eval-engineering is a skill for Claude Code, Codex from langchain-ai/langchain-skills. It costs 67 tokens per session (3,342 once invoked), scanned A, original, MIT.

A toolkit for evaluating software agents: checking an agent project, turning requirements into reviewed task descriptions, and preparing tasks and reusable project knowledge.

In plain words
What is it for?
Use it for agent evaluations, benchmark and task design, test environments, generated data, result checking, and Harbor test runs.
Why use it?
It helps make agent tests consistent and reviewable instead of relying on informal checks.

Skill for Claude CodeCodex ✓ vendor

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: reads .claude/ paths.

Part of the langchain-skills plugin — 22 skills shipped together

not rated 1.3krepo +19 4d ago A scan Socket: passSnyk: warnSkillSpector: pass 67 tokens original MIT

Good fit Use it for agent evaluations, benchmark and task design, test environments, generated data, result checking, and Harbor test runs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/langchain-ai/langchain-skills/eval-engineering
About the project

LangChain Skills is a collection of agent skills for building software agents with LangChain, LangGraph, and Deep Agents. Coding agents that support the Agent Skills specification, including Claude Code, Cursor, and Windsurf, can install and use these skills. The catalogue lists the project's skills and its Claude Code plugin.

langchain-ai/langchain-skills · 1,313 stars · on GitHub

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.

Any agent
npx skills add langchain-ai/langchain-skills --skill eval-engineering
Clone the repo
git clone --depth 1 https://github.com/langchain-ai/langchain-skills

Made for: Claude Code, Codex.

Or install langchain-skills, the plugin that ships this one along with the rest of its 22 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 eval-engineering

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/langchain-ai/langchain-skills/eval-engineering"><img src="https://agentmods.dev/badge/skills/langchain-ai/langchain-skills/eval-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,342 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. Third-party audits
  • Socket pass 21 Aug 2026
  • Snyk warn 21 Aug 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00067 $0.03342
Opus 5.5 $0.00027 $0.01337
Sonnet 5.5 $0.00013 $0.00668
Haiku 4.5 $0.00007 $0.00334

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

Security

Grade A, and why

eval-engineering 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 5 executable files (references/multi-turn-simulation/harbor_example.py, references/multi-turn-simulation/model_user.py, references/multi-turn-simulation/runner.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.

config/skills/eval-engineering/SKILL.md · 315 lines

How it starts

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

Eval Engineering

Flow

  • Inspect all inputs first: the repository, Harness, optional traces, existing Tasks and runs, existing World knowledge, and the human goal. Identify the source files and skill references that apply before proposing work.
  • Create or update the small project World Knowledge Skill from reusable facts in those inputs. Use it to propose one grounded Task.
  • Draft the Task Spec and World Skill together. Show both to the user, keep exact Task truth only in Task.md, and refine both until the user approves them.
  • Implement the approved Task, validate its Environment and Verifier, run the real Harness, inspect the full evidence, and fix only non-agent failures.
  • Reconcile the World Skill with what the run proved, then repeat this flow for the next Task.

Terms

  • Task Spec: Task.md, which describes the input, relevant agent conditions, Environment, scoring, fairness, and open decisions for one Task.
  • Task: the runnable instruction, Environment, and Verifier.
  • Harness: the complete agent Harbor runs, including prompts, model loop, tools, hooks, memory, sessions, and adapter.
  • Environment: the files, data, services, identity, permissions, network, clock, and mutable state around the Harness.
  • Verifier: independent checks that score the result or mark a run invalid.
  • World Knowledge Skill: a repository-local skill with reusable project-specific knowledge, references, scripts, assets, and tests that help generate Task Specs and build future Tasks.
  • Spec2Task: the full loop that turns a reviewed Task Spec into an audited runnable Task. Follow Task implementation for its concrete build order and reference routing.

Reference routing

Read each reference when its decision appears:

Need Read
Inspect source, traces, the Harness, dependencies, access, and existing evals Discovery
Bootstrap or update reusable project knowledge World knowledge
Propose Tasks and write the single Task Spec Task design
Build data, services, access, state, and reset Environment building
Create structured or natural-language data Synthetic data
Define independent evidence and scoring Verifier design
Apply Spec2Task to turn a reviewed Spec into an audited Task Task implementation
Compare model runs and classify failures Calibration
Package and run Harbor tasks Harbor
Adapt a known benchmark design Benchmark patterns
Build multi-turn conversations Multi-turn simulation
See World knowledge learned across two Tasks Service-desk example

Read the full file on GitHub · 315 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 · 315 lines · 67 tokens per session scan A 47c93e705a3a

Subscribe to this mod's changes

eval-engineering is a skill published in the GitHub repository langchain-ai/langchain-skills (1,313 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 3,342 once invoked, about $0.0003 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

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens