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.
curl -O https://raw.githubusercontent.com/AgentEvalHQ/AgentEval/main/.github/instructions/assertions.instructions.mdgit clone --depth 1 https://github.com/AgentEvalHQ/AgentEvalWrote 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/agentevalhq/agenteval/assertions)<a href="https://agentmods.dev/instructions/agentevalhq/agenteval/assertions"><img src="https://agentmods.dev/badge/instructions/agentevalhq/agenteval/assertions/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.
<a href="https://agentmods.dev/instructions/agentevalhq/agenteval/assertions"><img src="https://agentmods.dev/badge/instructions/agentevalhq/agenteval/assertions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00629 | $0.00629 |
| Opus 5.5 | $0.00252 | $0.00252 |
| Sonnet 5.5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
AgentEval assertions.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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assertion Implementation Guidelines
Core Assertion Pattern
All assertions follow the fluent pattern with chainable methods:
result.ToolUsage!.Should()
.HaveCalledTool("Tool1")
.BeforeTool("Tool2")
.WithArgument("key", "value")
.And() // Return to parent assertions
.HaveNoErrors();
Adding New Assertion Method
- Add to appropriate assertions class:
ToolUsageAssertions,PerformanceAssertions, orResponseAssertions - Always add
[StackTraceHidden]attribute to keep stack traces clean - Accept optional
becauseparameter for documentation - Use
AgentEvalScope.FailWith()for rich error messages
Assertion Method Template
/// <summary>Assert that XYZ condition is met.</summary>
/// <param name="expected">The expected value.</param>
/// <param name="because">Optional reason for the assertion.</param>
[StackTraceHidden]
public ToolUsageAssertions HaveXyz(string expected, string? because = null)
{
if (!ConditionMet(expected))
{
AgentEvalScope.FailWith(
ToolAssertionException.Create(
$"Expected XYZ to be '{expected}', but it was not.",
expected: expected,
actual: _actualValue,
suggestions: new[] { "Try doing X", "Check Y" },
because: because));
}
return this;
}
Error Message Structure
All failure messages MUST include:
- Expected: What was expected
- Actual: What was found
- Suggestions: Actionable hints (when applicable)
- Because: User's reason (if provided)
Example output:
Expected tool 'SearchTool' to be called because query requires search.
Expected: Tool 'SearchTool' called at least once
Actual: Tools called: [CalculateTool, FormatTool]
Suggestions:
→ Verify the agent has access to the expected tools
→ Check if the prompt clearly requests tool usage
Exception Types
ToolAssertionException- Tool-related assertion failuresPerformanceAssertionException- Performance/cost assertion failuresResponseAssertionException- Response content assertion failuresAgentEvalScopeException- Multiple failures collected in scope
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.
- 2mo ago First seen · 88 lines · 629 tokens per session scan A ca5cdbc35aed
AgentEval assertions.instructions.md is an instructions file published in the GitHub repository AgentEvalHQ/AgentEval (157 stars, last pushed 4d ago), licensed MIT. It adds 629 tokens to every session, about $0.0025 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.
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).
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.
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).
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.
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).
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.