nunit AGENTS.md

AGENTS.md instructions for nunit/nunit, covering agents.md, on every change, required cli tool, build & test quick reference and project conventions.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/nunit/nunit/agents-md
Clone the repo
git clone --depth 1 https://github.com/nunit/nunit

Made for: Codex, OpenCode.

Per session 655 This file is loaded in full into every session.
When invoked 655 The same file — it is already loaded in full.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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 $0.00655 $0.00655
Opus 5 $0.00328 $0.00328
Sonnet 5 $0.00131 $0.00131
Haiku 4.5 $0.00065 $0.00065

Measured today against content hash 77819d82c9bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

nunit AGENTS.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 today.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- **Debian/Ubuntu**: `sudo apt-get install -y dotnet-sdk-10.0`
AGENTS.md · 42 lines

How it starts

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

AGENTS.md

On every change

Before pushing or opening a PR, the agent MUST:

  1. Verify the .NET SDK is available (see below). Install it if missing, or ask the user if elevation is required.
  2. Keep the change scoped — only modify files related to the stated task. If the IDE, LSP, or package tooling touched unrelated files, revert those before committing. One topic per PR. No unnecessary refactoring.
  3. Build clean: dotnet build nunit.slnx -c Release. No new warnings. Fix warnings in code you wrote — don't #pragma warning disable.
  4. Test: dotnet test nunit.slnx -c Release.
  5. Push and open the PR only after build and tests pass. Never push a failing build.

If a step fails, fix and re-run — don't bypass.

Required CLI tool

The agent needs .NET 10 SDK or newer on PATH — check with dotnet --list-sdks. git is assumed; IDEs aren't required.

If the SDK isn't installed, try the platform package manager:

  • Windows: winget install Microsoft.DotNet.SDK.10
  • macOS: brew install --cask dotnet-sdk
  • Debian/Ubuntu: sudo apt-get install -y dotnet-sdk-10.0

If the install needs elevation (sudo, admin) or the package manager itself is missing, stop and ask the user. For example:

".NET 10 SDK isn't installed and I don't have permission to install it. Please run winget install Microsoft.DotNet.SDK.10 (or download from https://dotnet.microsoft.com/download) and confirm when done."

Don't invent workarounds — the build genuinely requires the SDK.

Build & test quick reference

  • Solution: nunit.slnx in repo root.
  • Target frameworks in build output: net8.0, net6.0, net462. A full build produces binaries for each.
  • Test projects (the ones to actually run): nunit.framework.tests-*, nunit.framework.legacy.tests-*, nunitlite.tests-*. Other test projects contain intentionally-failing fixtures used by integration tests — IMPORTANT DONT "fix" their failures.
  • Full packaging build (only needed for releases, not per-change): ./build.ps1 --target=Test --configuration=Release on Windows, ./build.sh --target=Test --configuration=Release on Linux/Mac. See BUILDING.md for all Cake targets.

Read the full file on GitHub · 42 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. today First seen · 42 lines · 655 tokens per session scan B 77819d82c9bf

Subscribe to this mod's changes

nunit AGENTS.md is an instructions file published in the GitHub repository nunit/nunit (2,622 stars, last pushed 2d ago), licensed MIT. It adds 655 tokens to every session, about $0.0033 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Related

Other instructions, from other repositories