AgentEval: Instructions file for GitHub Copilot

.github/instructions/docfx.instructions.md

AgentEval docfx.instructions.md is an instructions file for GitHub Copilot from AgentEvalHQ/AgentEval. It costs 1,268 tokens per session, scanned B, original, MIT.

A set of instructions for DocFX, a tool that turns .NET source code and Markdown files into a documentation website, in the AgentEval project. It describes the documentation folders, configuration, templates, and build process.

In plain words
What is it for?
Use it when editing AgentEval docs, changing DocFX settings, generating API metadata, or building the documentation website.
Why use it?
It gives contributors a consistent way to generate API reference pages and the rest of the documentation site. This avoids configuration mistakes and unclear build steps.

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 →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is "src": [{ "src": "../src", "files": ["**/*.csproj"], "exclude": ["AgentEval.MAF.AgentHooks/**"] }],.

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/docfx.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 docfx.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/agentevalhq/agenteval/docfx"><img src="https://agentmods.dev/badge/instructions/agentevalhq/agenteval/docfx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,268 This file is loaded in full into every session.
When invoked 1,268 The same file — it is already loaded in full.
Security scan B 1 finding. 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.01268 $0.01268
Opus 5.5 $0.00507 $0.00507
Sonnet 5.5 $0.00254 $0.00254
Haiku 4.5 $0.00127 $0.00127

Measured 23d ago against content hash 209edfaba3da, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

AgentEval docfx.instructions.md scanned grade B with 1 finding 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 23d 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- [ ] `docfx build` completes without warnings
.github/instructions/docfx.instructions.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DocFX Instructions for AgentEval

Instructions for working with DocFX documentation generation in AgentEval

Project Setup

File Structure

docs/
├── docfx.json          # Main configuration
├── toc.yml             # Navigation structure
├── index.md            # Landing page
├── api/                # Generated API YAML (git-ignored for *.yml)
├── _site/              # Generated HTML output (git-ignored)
├── images/             # Static images
├── templates/          # Custom templates (material theme)
├── adr/                # Architecture Decision Records
└── showcase/           # Code gallery and examples

Key Configuration (docfx.json)

{
  "metadata": [{
    "src": [{ "src": "../src", "files": ["**/*.csproj"], "exclude": ["AgentEval.MAF.AgentHooks/**"] }],
    "dest": "api",
    "properties": { "TargetFramework": "net10.0" }
  }],
  "build": {
    "template": ["default", "modern", "templates/material"],
    "output": "_site"
  }
}

Build Commands

Full Build (Recommended)

# From repository root
.\scripts\build-documentation.ps1

Step-by-Step

# 1. Build project (generates XML docs)
dotnet build src\AgentEval\AgentEval.csproj --configuration Release

# 2. Generate API metadata (YAML files)
cd docs
docfx metadata

# 3. Build HTML site
docfx build

# 4. Preview locally
docfx serve _site
# Opens at http://localhost:8080

Quick Rebuild (Markdown only)

# Skip metadata regeneration if only editing .md files
cd docs
docfx build
start _site\index.html

Common Issues & Solutions

Issue: API docs not generating

Cause: XML documentation disabled in csproj Fix: Ensure <GenerateDocumentationFile>true</GenerateDocumentationFile> in csproj

Issue: docfx metadata fails

Cause: Build errors in source code Fix: Run dotnet build first and fix any compilation errors

Cause: A project that does not target net10.0. docfx metadata builds every project at the TargetFramework set in docfx.json, so a project without that target has no restored references and fails with CS0246. AgentEval.MAF.AgentHooks (net8.0 only, experimental, not packaged) is excluded for this reason. Fix: Exclude the project in metadata.src.exclude, or add the net10.0 target to it.

Read the full file on GitHub · 178 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. 23d ago Changed · +5 lines · +116 tokens per session 209edfaba3da
  2. 26d ago Changed · +40 tokens per session 536087dd3fa5
  3. 2mo ago First seen · 173 lines · 1,112 tokens per session scan B aff3e7289b55

Subscribe to this mod's changes

AgentEval docfx.instructions.md is an instructions file published in the GitHub repository AgentEvalHQ/AgentEval (157 stars, last pushed 4d ago), licensed MIT. It adds 1,268 tokens to every session, about $0.0051 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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