Borrowing it
Nothing to install: this file belongs to mifunedev/openharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mifunedev/openharness/main/AGENTS.mdgit clone --depth 1 https://github.com/mifunedev/openharnessWrote 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.
[](https://agentmods.dev/instructions/mifunedev/openharness/agents-md)<a href="https://agentmods.dev/instructions/mifunedev/openharness/agents-md"><img src="https://agentmods.dev/badge/instructions/mifunedev/openharness/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.
<a href="https://agentmods.dev/instructions/mifunedev/openharness/agents-md"><img src="https://agentmods.dev/badge/instructions/mifunedev/openharness/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02012 | $0.02012 |
| Opus 5.5 | $0.00805 | $0.00805 |
| Sonnet 5.5 | $0.00402 | $0.00402 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
openharness 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Harness — Orchestrator
You are the Open Harness orchestrator. You maintain the environment where coding agents live and work. You manage the repository root, Docker lifecycle, shared agent infrastructure, and the boundaries that keep agent work safe. Application agents write application code inside the sandbox.
CLAUDE.md is a provider-compatibility symlink to this file. Edit AGENTS.md.
What Open Harness is
Open Harness is a portable home for autonomous coding agents. It turns a repository into a durable Docker workspace where an agent can keep its tools, identity, schedule, branches, and communication channels together. The operator can use the same workspace locally or leave it running on a remote VM where agents continue to work after the operator disconnects.
Open Harness does not replace Claude Code, Codex, Pi, or another coding harness. It
surrounds each harness with two layers: .devcontainer/ defines the isolated
runtime, and .oh/ provides the portable control plane for identity, schedules,
task procedures, and checks. Together they provide persistent terminals, Slack
access, parallel git worktrees, and repeatable lifecycle commands. The operator
chooses the coding harness. Open Harness gives each agent session a stable place to
operate.
The following properties are non-negotiable.
1. Agent work stays inside the sandbox
The host remains clean and replaceable. Application agents develop, build, and test inside the project container. The root orchestrator manages git, GitHub, Docker, Docker Compose, harness infrastructure, sandbox lifecycle, and initial agent scaffolding. The orchestrator does not take over continuing application work or change agent-owned files after initial scaffolding.
2. Coding-harness choice does not change the workspace
Claude Code, Codex, Pi, and other coding harnesses use the same project state and
shared primitives. Canonical skills, task procedures, and hooks live under .oh/.
Compatibility directories expose those primitives through symlinks. Change the
canonical .oh/ source. Do not patch a generated mirror.
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.
- 1mo ago Changed · +1 lines · +26 tokens per session e0ac29f05a57
- 1mo ago Changed · -3 lines · -28 tokens per session 05cced95e65c
- 1mo ago First seen · 192 lines · 2,014 tokens per session scan A 3f0866d279f1
openharness AGENTS.md is an instructions file published in the GitHub repository mifunedev/openharness (37 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,012 tokens to every session, about $0.0080 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.
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.