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.
npx agentmods add instructions/agentevalhq/agenteval/metricsgit clone --depth 1 https://github.com/AgentEvalHQ/AgentEvalWhat 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.
| Model | Per session | Once 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 |
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.
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_faithfulnesscode_= Computed by code (free) →code_tool_successembed_= Embedding-based (costs embedding API) →embed_answer_similarity
Interface Selection
IRAGMetric- For metrics that evaluate retrieval-augmented generation- Set
RequiresContext = trueif context documents needed - Set
RequiresGroundTruth = trueif expected answer needed
- Set
IAgenticMetric- For metrics that evaluate agent tool usage- Set
RequiresToolUsage = true
- Set
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
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.
- 2d ago First seen · 85 lines · 698 tokens per session scan A f5b1d39d232e
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.
Other instructions, from other repositories
zeroclaw CLAUDE.md
Instructions for zeroclaw-labs/zeroclaw, covering claude.md — zeroclaw (claude code), claude code settings, hooks and slash commands.
openagent CLAUDE.md
Claude Code instructions for the-open-agent/openagent, covering claude.md, commands, architecture, backend (go / beego) and frontend (react).
Tracely-ai CLAUDE.md
Claude Code instructions for Jwuthri/Tracely-ai, covering claude.md, commands, architecture, hard rules and gotchas.
nuwax AGENTS.md
Instructions for nuwax-ai/nuwax, covering ai agent system documentation, 系统概述, ai agent 架构, 核心组件 and ai 功能特性.
zhin zhin-plugin.instructions.md
Instructions for zhinjs/zhin, covering zhin plugin runtime authoring, package contract, convention directories, imports and native typescript and command routes.
OpenPersona AGENTS.md
Instructions for acnlabs/OpenPersona, covering agents.md, project overview, setup, project structure and architecture rules.