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/harness/harness-evals/agents-mdgit clone --depth 1 https://github.com/harness/harness-evalsWrote 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.
[](https://agentmods.dev/instructions/harness/harness-evals/agents-md)<a href="https://agentmods.dev/instructions/harness/harness-evals/agents-md"><img src="https://agentmods.dev/badge/instructions/harness/harness-evals/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.05922 | $0.05922 |
| Opus 5 | $0.02961 | $0.02961 |
| Sonnet 5 | $0.01184 | $0.01184 |
| Haiku 4.5 | $0.00592 | $0.00592 |
Grade A, and why
harness-evals AGENTS.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 3d 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - harness-evals
Project Overview
harness-evals is an open-source AI evaluation framework for LLM agents, prompts, and structured outputs. It provides a pip install-able scoring engine with 70+ metrics across deterministic, structural, operational, reliability, predictability, MCP, similarity, LLM-judged, RAG, safety, agent, conversation, and security categories.
Core principle: An eval always produces a Score. Every metric is a single class with a measure() method.
Data flow: Golden (authored) + agent output -> EvalCase (evaluated) -> Score (result)
Language: Python 3.10+
License: Apache 2.0
Package name: harness-evals
Import name: harness_evals
Build System
pip install -e "." # Core only (deterministic metrics, no LLM key needed)
pip install -e ".[llm]" # + OpenAI, Anthropic for LLM-judged metrics
pip install -e ".[otlp]" # + OTLP metrics & traces export
pip install -e ".[langfuse]" # + Langfuse source/sink
pip install -e ".[similarity]" # + BLEU metric (nltk)
pip install -e ".[harness]" # + Harness AI Service LLM provider
pip install -e ".[benchmarks]" # + Academic benchmarks (MMLU, GSM8K, HumanEval, etc.)
pip install -e ".[all]" # Everything
pip install -e ".[all,dev]" # Everything + dev tools
Build tool: Poetry via pyproject.toml (backend: poetry-core)
No compiled extensions — pure Python.
Testing
pytest tests/ -v # All tests
pytest tests/ -v -m unit # Unit tests only
pytest tests/metrics/ -v # Specific directory
pytest tests/test_core.py -v # Specific file
pytest tests/test_core.py::test_evaluate -v # Specific function
pytest tests/ --cov=harness_evals --cov-report=html # With coverage
- Mark tests:
@pytest.mark.unit,@pytest.mark.integration - Test data:
tests/data/
ALWAYS run pytest tests/ -v before committing.
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.
- 3d ago First seen · 478 lines · 5,922 tokens per session scan A 1fd9c3a133a7
harness-evals AGENTS.md is an instructions file published in the GitHub repository harness/harness-evals (24 stars, last pushed 5d ago), licensed Apache-2.0. It adds 5,922 tokens to every session, about $0.0296 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
GPT-RAG release.instructions.md
Instructions for Azure/GPT-RAG, a project described as: Sharing the learning along the way we been gathering to enable Azure OpenAI at enterprise scale in a secure manner. GPT-RAG core is a Retrieval-Augmented Generation pattern running in Azure, using Azure Cognitive Search for retrieval and Azure OpenAI large…
plamen CLAUDE.md
Claude Code instructions for PlamenTSV/plamen, covering plamen — security auditor, execution model, reference files and shared.
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
ZipAI CLAUDE.md
Claude Code instructions for nickdesi/ZipAI, covering claude.md — zipai: ultra-dense token optimizer, rules, 1. zero filler, 2. ambiguity and 3. prompt caching.
TreeSkill CLAUDE.md
Instructions for JimmyMa99/TreeSkill, covering claude.md, project overview, commands, install and run tests.
tshark-mcp copilot-instructions.md
Copilot instructions for ouonet/tshark-mcp: Project: MCP server for using TShark to analyze network packets. Language: Python.