loopgate_harness: Instructions file for Codex

AGENTS.md

loopgate_harness AGENTS.md is an instructions file for Codex, OpenCode from rxdt/loopgate_harness. It costs 789 tokens per session, scanned C, original, MIT.

Project instructions for Loopgate Harness, including repository boundaries, forbidden files, quality checks, documentation, and commit rules. A harness is a set of checks that controls how work is validated.

In plain words
What is it for?
Use them when modifying Loopgate Harness, running lint, formatting, type checks, tests, preflight checks, and the final gate.
Why use it?
They keep agents from changing protected parts of the repository and define what must pass before work is considered complete.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rxdt/loopgate_harness/agents-md"><img src="https://agentmods.dev/badge/instructions/rxdt/loopgate_harness/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 789 This file is loaded in full into every session.
When invoked 789 The same file — it is already loaded in full.
Security scan C 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.00789 $0.00789
Opus 5.5 $0.00316 $0.00316
Sonnet 5.5 $0.00158 $0.00158
Haiku 4.5 $0.00079 $0.00079

Measured 1mo ago against content hash 724d7a423100, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

loopgate_harness AGENTS.md scanned grade C 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 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Never run destructive git commands (`rm -rf`, `git reset --hard`, `git branch -D`) unless the user explicitly asks; verify each risky step.
AGENTS.md · 90 lines

How it starts

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

FUNCTIONALITY

Repository boundary

  • Work only inside this repository; create and use scratchpad/ for temporary files.
  • Do not read, write, or search outside the repo unless the user explicitly asks.
  • Do not edit forbidden paths: AGENTS.md, .githooks/, harness/, preferences/ .github/, pyproject.toml. The gate enforces this.
  • Do not make assumptions. Check the code before moving forward.

Quality

  • The quality minimum is code in harness/gate.py (forbidden to agents). Leave it unchallenged.
  • Strengthen tests and coverage. Pass lint, type, and gate checks.
  • Avoid lint suppressions, type-ignores, skipped/xfail tests, or broad exception swallowing.
  • Never run destructive git commands (rm -rf, git reset --hard, git branch -D) unless the user explicitly asks; verify each risky step.
  • Never bypass or reconfigure git hooks.

Commit and gate

  • ralph harness preflight runs on commit => fast lint + format check + plus loop containment.
  • Run harness preflight often, run harness gate before pushing
  • Done means: no forbidden path touched; ralph harness gate is green; your chosen spec and docs/PROJECT_STATUS.md reflect what was built.

Documentation

  • Every agent-maintained .md (docs/PROJECT_STATUS, docs/specs/) stays under 100 lines — distill for the next agent.

Session handoff

  • At <=40% of your context window, stop expanding scope.
    • Update docs/PROJECT_STATUS.md with new state, checks, commit/branch, blockers, and next steps.
    • Update your spec.
    • Leave the repo resumable.
    • Commit through the gate, push, then merge when safe.

RULES

1. Think First

Verify assumptions. Surface confusion. Note tradeoffs.

Before implementing:

  • State assumptions explicitly. If uncertain, ask.
  • If multiple interpretations exist, present them - don't pick silently.
  • If a simpler approach exists, say so. Push back when warranted.
  • If something is unclear, stop. Request clarity.
  • Review source code and tests.

Read the full file on GitHub · 90 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. 1mo ago Changed · +9 lines · +62 tokens per session 724d7a423100
  2. 1mo ago First seen · 81 lines · 727 tokens per session scan C 4b74cce9ddfb

Subscribe to this mod's changes

loopgate_harness AGENTS.md is an instructions file published in the GitHub repository rxdt/loopgate_harness (25 stars, last pushed 28d ago), licensed MIT. It adds 789 tokens to every session, about $0.0032 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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