research-closure-harness: Instructions file for Codex

AGENTS.md

research-closure-harness AGENTS.md is an instructions file for Codex, OpenCode from Shiien/research-closure-harness. It costs 868 tokens per session, scanned A, original, MIT.

A set of instructions for completing research work with evidence and a finished draft. It requires checking the project's research state, logs, claim graph, protocol, and workflow tools before substantial work.

In plain words
What is it for?
Use it to check research workflow status, identify the next ready probe, enforce scope rules, track claims and outcomes, and help finish a defensible research unit.
Why use it?
It prevents new experiments or research questions from starting while required evidence, records, or unresolved issues are still missing.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/shiien/research-closure-harness/agents-md.svg)](https://agentmods.dev/instructions/shiien/research-closure-harness/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/shiien/research-closure-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/shiien/research-closure-harness/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 868 This file is loaded in full into every session.
When invoked 868 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.00868 $0.00868
Opus 5 $0.00434 $0.00434
Sonnet 5 $0.00174 $0.00174
Haiku 4.5 $0.00087 $0.00087

Measured 8d ago against content hash 07a72c3a8cb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

research-closure-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 8d 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 · 120 lines

How it starts

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

Research Closure Rules for Codex

Mission

Help the researcher finish a defensible research unit. Optimize for closure, evidence, and a complete draft—not for generating the largest number of ideas.

Before substantial work, read:

  1. .research/state.json
  2. the current sprint log under .research/logs/
  3. the active experiment card, if any
  4. .research/claim_graph.json — the claim graph is the engine: it must exist and validate before a sprint can be frozen
  5. docs/protocol.md

Run:

python tools/research_closure.py guard
python tools/claim_graph.py frontier
python tools/research_closure.py next

The guard reports blocking violations; frontier shows which probe is ready to run; next shows the event the harness expects from you. If the guard reports a blocking violation, do not begin a new method, experiment family, benchmark, or research question. Help resolve the violation first.

For human progress tracking, run python tools/research_closure.py dashboard to open the interactive DAG view (theory → variables/edges → probes, with outcomes, frontier and the resolution map).

Non-negotiable workflow

Every task must map to the current frozen claim and to a probe of the claim graph.

Before implementing a new experiment, identify:

  • research question
  • falsifiable hypothesis
  • single primary intervention
  • measurement
  • expected artifact
  • kill criterion
  • time budget

Every experiment must name the claim-graph probe it runs (new-experiment --node Pn). If no active experiment card exists, create one with the CLI before implementation. If the claim graph does not exist yet, author it first: claim_graph.py init --claim "...", then add-variable / add-edge / add-absent / add-probe / add-resolution, then validate.

After obtaining results, do not immediately create another variant. First:

  1. summarize evidence;
  2. classify the result as supported, falsified, inconclusive, or terminated;
  3. write a decision;
  4. close the experiment with the CLI;
  5. update the draft or result note.

Read the full file on GitHub · 120 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. 8d ago First seen · 120 lines · 868 tokens per session scan A 07a72c3a8cb6

Subscribe to this mod's changes

research-closure-harness AGENTS.md is an instructions file published in the GitHub repository Shiien/research-closure-harness (10 stars, last pushed 14d ago), licensed MIT. It adds 868 tokens to every session, about $0.0043 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-31.

Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens