h2 AGENTS.md

A project guide for AI coding assistants, covering test isolation, commit checks, versioning, and the release process.

In plain words
What is it for?
Running isolated tests, checking commits, choosing version increments, updating the changelog, and building releases.
Why use it?
It prevents tests from changing a developer’s real settings and helps ensure releases pass the required checks.

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/dcosson/h2/agents-md
Clone the repo
git clone --depth 1 https://github.com/dcosson/h2

Made for: Codex, OpenCode.

Per session 305 This file is loaded in full into every session.
When invoked 305 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00305 $0.00305
Opus 5 $0.00152 $0.00152
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

Measured 2d ago against content hash b66f628862b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

h2 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 29 lines

What it actually says

Testing Rules

Never use config.ConfigDir() in tests. Tests must not touch the real h2 config directory. Use setupFakeHome(t) or a similar pattern that sets H2_DIR to a temp directory and calls config.ResetResolveCache(). This prevents test side effects on the real ~/.h2 directory and ensures test isolation.

Release Process

Commit Quality Gate

Before every feature commit, run make check and ensure it passes.

When doing a production release, follow this sequence:

  1. Ensure you are on the main branch first.
  2. Fetch and fast-forward main to origin/main (git fetch origin main && git pull --ff-only origin main).
  3. Determine the version bump and update the h2 version:
    • If unsure what bump to use, ask the user.
    • Use semver rules:
      • patch for non-breaking changes.
      • for pre-1.0 versions: minor for breaking changes.
      • for 1.0+ versions: major for breaking changes.
  4. Update docs/CHANGELOG.md with changes since the last version tag and its tagged commit.
  5. Run all test suites and ensure they pass.
  6. Run make check and ensure it passes.
  7. Run make build-release and ensure it passes.
  8. Tag the current HEAD with the release version.
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. 2d ago First seen · 29 lines · 305 tokens per session scan A b66f628862b2

Subscribe to this mod's changes

h2 AGENTS.md is an instructions file published in the GitHub repository dcosson/h2 (159 stars, last pushed 6d ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 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-30.

Related

Other instructions, from other repositories

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

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

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,182 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,345 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

next.js 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