repository-harness: Instructions file for Codex

AGENTS.md

repository-harness AGENTS.md is an instructions file for Codex, OpenCode from hoangnb24/repository-harness. It costs 237 tokens per session, scanned A, original, MIT.

A set of instructions for working in repository-harness, a project that tests and guides coding-agent work. It explains which repository documents are authoritative and when changes or planning files are needed.

In plain words
What is it for?
Investigating requests, implementing bounded changes, validating results, coordinating longer work, and reporting reusable problems agents encounter.
Why use it?
It prevents agents from changing files during read-only tasks or making policy decisions without checking the project's source of truth.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is hoangnb24/repository-harness's own configuration. It tells Codex and OpenCode how to work on repository-harness 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 repository-harness configures →

About the project

repository-harness is a repository protocol that makes a software codebase easier for coding agents to understand and work on safely. It is for teams using Claude Code, Codex, Cursor, and similar agents who need authoritative documents, durable plans, explicit decision boundaries, and evidence for completed work. Its catalogue entries install the protocol's skills and instructions.

hoangnb24/repository-harness · 1,256 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to hoangnb24/repository-harness. 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/hoangnb24/repository-harness/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/hoangnb24/repository-harness

Made for: Codex, OpenCode.

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 repository-harness AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hoangnb24/repository-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/hoangnb24/repository-harness/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 237 This file is loaded in full into every session.
When invoked 237 The same file — it is already loaded in full.
Security scan A 0 findings. 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.00237 $0.00237
Opus 5.5 $0.00095 $0.00095
Sonnet 5.5 $0.00047 $0.00047
Haiku 4.5 $0.00024 $0.00024

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

Security

Grade A, and why

repository-harness 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 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.

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.

AGENTS.md · 25 lines

What it actually says

Agent Instructions

Harness

Start with the requested outcome and use the repository as the system of record. Find the relevant code, interfaces, commands, tests, and evidence through the repository map in docs/README.md. docs/WORKFLOW.md describes repository understanding, missing capabilities, authority, and trust.

  • Respect the requested scope. Inspection does not authorize edits or operation.
  • Prefer source references over duplicate summaries. Preserve product intent and rationale that code and tests do not express.
  • Identify missing capabilities needed to act, observe, or verify. Report what is unavailable or unproven instead of inventing commands or claiming success.
  • Before changing externally observable policy, establish repository authority. Stop at material unresolved choices; configurable defaults are not authority.
  • Preserve user-owned state and use the repository's native safety and validation checks. Explain observed results and their limits.
  • Only invoke a Harness skill when the user explicitly requests it.

Consumer repositories own their task workflow and planning. Harness provides context and optional tools, without a task database or orchestration lifecycle.

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 · -7 lines · -95 tokens per session d034c93fcce8
  2. 1mo ago First seen · 32 lines · 332 tokens per session scan A 745a9e87a0f3

Subscribe to this mod's changes

repository-harness AGENTS.md is an instructions file published in the GitHub repository hoangnb24/repository-harness (1,256 stars, last pushed 23d ago), licensed MIT. It adds 237 tokens to every session, about $0.0009 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.

Related

Other instructions, from other repositories

agent-rulescope tests.instructions.md

Instructions for 13624725933/agent-rulescope, a project described as: See exactly which instructions your coding agent inherits. Scan AGENTS.md, CLAUDE.md, Cursor and Copilot rules.

13624725933/agent-rulescope · 38 tokens

agent-rulescope copilot-instructions.md

Copilot instructions for 13624725933/agent-rulescope, a project described as: See exactly which instructions your coding agent inherits. Scan AGENTS.md, CLAUDE.md, Cursor and Copilot rules.

13624725933/agent-rulescope · 25 tokens

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,786 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