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/maf-updatesgit 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.03171 | $0.03171 |
| Opus 5 | $0.01586 | $0.01586 |
| Sonnet 5 | $0.00634 | $0.00634 |
| Haiku 4.5 | $0.00317 | $0.00317 |
Grade A, and why
AgentEval maf-updates.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 yesterday.
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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAF Update & Breaking Change Instructions
These instructions apply when updating the Microsoft Agent Framework (MAF) NuGet dependency in AgentEval.
Two-Phase Upgrade Workflow
MAF upgrades follow two phases:
Phase 1 (OPTIONAL): maf-upgrade-preparation.instructions.md
Diff MAF source → produce plan document
Output: MAF/MAF-Upgrade-Plan.md
Phase 2 (THIS FILE): Update NuGet → fix breaks → run tests
Input: plan document (if available) OR compile errors
Phase 1 is recommended for major MAF version changes. For minor/patch updates or Dependabot PRs, start directly at Step 0 below.
Step 0: Check for an Existing Upgrade Plan
Before starting, check if MAF/MAF-Upgrade-Plan.md exists.
- If it exists: Read it first. It contains pre-analyzed breaking changes, behavioral changes, and concrete fix code snippets produced by Phase 1. Use it as a guide — you already know what will break and how to fix it.
- If it doesn't exist: Proceed normally with build-error-driven detection (Step 1).
Where MAF Versions Are Pinned
All MAF package versions are pinned in a single file:
Directory.Packages.props
Look for these three entries:
<PackageVersion Include="Microsoft.Agents.AI" Version="..." />
<PackageVersion Include="Microsoft.Agents.AI.OpenAI" Version="..." />
<PackageVersion Include="Microsoft.Agents.AI.Workflows" Version="..." />
All three MUST be updated to the same version simultaneously.
Also update the Microsoft.Extensions.AI packages if the MAF release requires a newer version:
<PackageVersion Include="Microsoft.Extensions.AI" Version="..." />
<PackageVersion Include="Microsoft.Extensions.AI.OpenAI" Version="..." />
<PackageVersion Include="Microsoft.Extensions.AI.Evaluation.Quality" Version="..." />
Current versions — always check Directory.Packages.props for the actual pinned versions.
Which projects reference which MAF packages:
src/AgentEval.MAF/AgentEval.MAF.csproj→Microsoft.Agents.AI,Microsoft.Agents.AI.Workflows(compile-time dependency)src/AgentEval/AgentEval.csproj(umbrella) →Microsoft.Agents.AI,Microsoft.Agents.AI.Workflows(re-declared for NuGet consumers becausePrivateAssets="all"suppresses transitive propagation from sub-projects)samples/AgentEval.Samples/AgentEval.Samples.csproj→Microsoft.Agents.AI.OpenAI,Microsoft.Agents.AI.Workflows
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.
- yesterday First seen · 248 lines · 3,171 tokens per session scan A bc76726b8a6e
AgentEval maf-updates.instructions.md is an instructions file published in the GitHub repository AgentEvalHQ/AgentEval (138 stars, last pushed yesterday), licensed MIT. It adds 3,171 tokens to every session, about $0.0159 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.