AgentEval: Instructions file for GitHub Copilot

.github/instructions/metrics.instructions.md

AgentEval metrics.instructions.md is an instructions file for GitHub Copilot from AgentEvalHQ/AgentEval. It costs 698 tokens per session, scanned A, original, MIT.

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

Written for GitHub Copilot: a Copilot instructions file.

This is AgentEvalHQ/AgentEval's own configuration. It tells GitHub Copilot how to work on AgentEval itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything AgentEval configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AgentEvalHQ/AgentEval. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AgentEvalHQ/AgentEval/main/.github/instructions/metrics.instructions.md
Clone the repo
git clone --depth 1 https://github.com/AgentEvalHQ/AgentEval

Made for: GitHub Copilot.

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/agentevalhq/agenteval/metrics/github.svg)](https://agentmods.dev/instructions/agentevalhq/agenteval/metrics)
Your own site
<a href="https://agentmods.dev/instructions/agentevalhq/agenteval/metrics"><img src="https://agentmods.dev/badge/instructions/agentevalhq/agenteval/metrics/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 AgentEval metrics.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/agentevalhq/agenteval/metrics"><img src="https://agentmods.dev/badge/instructions/agentevalhq/agenteval/metrics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. 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.00698 $0.00698
Opus 5.5 $0.00279 $0.00279
Sonnet 5.5 $0.00140 $0.00140
Haiku 4.5 $0.00070 $0.00070

Measured 2mo ago against content hash f5b1d39d232e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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. 2mo 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 (157 stars, last pushed 4d ago), licensed MIT. It adds 698 tokens to every session, about $0.0028 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 instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens