AgentEval metrics.instructions.md

A set of rules for adding evaluation metrics to AgentEval, a .NET toolkit for measuring AI-agent quality. It explains metric categories, naming prefixes, required inputs, and the standard C# structure.

In plain words
What is it for?
Use it when creating metrics for retrieval-augmented generation, tool usage, answer quality, context, or similarity in AgentEval.
Why use it?
It prevents new metrics from being named or classified inconsistently and makes their data requirements clear. It also distinguishes metrics that use paid model or embedding calls from those calculated in code.

Instructions file for GitHub Copilot

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 instructions/agentevalhq/agenteval/metrics
Clone the repo
git clone --depth 1 https://github.com/AgentEvalHQ/AgentEval

Made for: GitHub Copilot.

Per session 698 This file is loaded in full into every session.
When invoked 698 The same file — it is already loaded in full.
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.00698 $0.00698
Opus 5 $0.00349 $0.00349
Sonnet 5 $0.00140 $0.00140
Haiku 4.5 $0.00070 $0.00070

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

Security

Grade A, and why

AgentEval metrics.instructions.md 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 2d 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.

.github/instructions/metrics.instructions.md · 85 lines

How it starts

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

Metric Implementation Guidelines

Metric Naming Prefixes

ALL metrics MUST use these prefixes in their Name property:

  • llm_ = LLM-evaluated (costs API calls) → llm_faithfulness
  • code_ = Computed by code (free) → code_tool_success
  • embed_ = Embedding-based (costs embedding API) → embed_answer_similarity

Interface Selection

  • IRAGMetric - For metrics that evaluate retrieval-augmented generation
    • Set RequiresContext = true if context documents needed
    • Set RequiresGroundTruth = true if expected answer needed
  • IAgenticMetric - For metrics that evaluate agent tool usage
    • Set RequiresToolUsage = true

Standard Metric Structure

public class MyMetric : IRAGMetric
{
    private readonly IChatClient _evaluator;
    
    public string Name => "llm_my_metric";
    public string Description => "Evaluates XYZ quality";
    public bool RequiresContext => true;
    public bool RequiresGroundTruth => false;
    
    public MyMetric(IChatClient evaluator) => _evaluator = evaluator;
    
    public async Task<MetricResult> EvaluateAsync(
        EvaluationContext context, 
        CancellationToken ct = default)
    {
        // Validate required fields
        if (string.IsNullOrEmpty(context.Context))
            return MetricResult.Fail(Name, "Context is required");
        
        // Call LLM for evaluation
        var prompt = BuildEvaluationPrompt(context);
        var response = await _evaluator.GetResponseAsync([...], ct: ct);
        
        // Parse response (use LlmJsonParser for JSON responses)
        var parsed = LlmJsonParser.Parse<EvalResponse>(response.Text);
        
        return MetricResult.Pass(Name, parsed.Score, parsed.Explanation);
    }
}

Using LlmJsonParser

For LLM responses that return JSON, use the built-in parser:

var result = LlmJsonParser.Parse<T>(responseText);
// Handles markdown code blocks, extracts JSON, deserializes

Score Normalization

All scores should be 0-100 scale. Use ScoreNormalizer:

var normalized = ScoreNormalizer.From1To5(rawScore); // 1-5 → 0-100
var normalized = ScoreNormalizer.From0To1(rawScore); // 0-1 → 0-100

Read the full file on GitHub · 85 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. 2d ago First seen · 85 lines · 698 tokens per session scan A f5b1d39d232e

Subscribe to this mod's changes

AgentEval metrics.instructions.md is an instructions file published in the GitHub repository AgentEvalHQ/AgentEval (138 stars, last pushed 2d ago), licensed MIT. It adds 698 tokens to every session, about $0.0035 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.