What is openhermit AGENTS.md?

A set of working rules for coding agents in the OpenHermit repository. It covers how to change code, update documentation, run tests, and write commits.

It is for guiding incremental code changes, preserving clear module boundaries, updating README.md and docs, running npm run typecheck and npm test when needed, and writing concise English commit messages.

It reduces inconsistent changes and makes the agent check the relevant tests and documentation before calling work complete.

How HCF-STUDIOS/openhermit configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to HCF-STUDIOS/openhermit. 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/HCF-STUDIOS/openhermit/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/HCF-STUDIOS/openhermit

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/hcf-studios/openhermit/agents-md/github.svg)](https://agentmods.dev/instructions/hcf-studios/openhermit/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/hcf-studios/openhermit/agents-md"><img src="https://agentmods.dev/badge/instructions/hcf-studios/openhermit/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/hcf-studios/openhermit/agents-md"><img src="https://agentmods.dev/badge/instructions/hcf-studios/openhermit/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 549 This file is loaded in full into every session.

When invoked 549 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.

Model	Per session	Once invoked
Fable 5.1	$0.00549	$0.00549
Opus 5.5	$0.00220	$0.00220
Sonnet 5.5	$0.00110	$0.00110
Haiku 4.5	$0.00055	$0.00055

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

Security

Grade A, and why

openhermit 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 2mo 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 · 59 lines

How it starts

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

OpenHermit Workspace Rules

This file defines baseline collaboration rules for agents working in this repository.

General

Prefer small, incremental changes over large rewrites unless the task explicitly requires a redesign.
Keep behavior changes aligned with the current documented architecture before introducing new abstractions.
When changing a core flow, update the corresponding docs in README.md and docs/ in the same branch.
Do not preserve legacy compatibility unless the user explicitly asks for it.

Code Changes

Prefer clear module boundaries over oversized files.
Reuse existing helpers and shared abstractions before introducing new patterns.
Keep internal state and external state clearly separated.
Avoid adding hidden fallback paths that make behavior harder to reason about.

Testing

Run relevant tests after meaningful code changes.
For broad refactors or runtime changes, run:
- npm run typecheck
- npm test
Do not claim a fix is complete if the affected tests were not run.

Commits

Use English commit messages.
Keep commit messages concise and descriptive.
Prefer the format: <type>: <summary>
Common types:
- feat
- fix
- refactor
- test
- docs
- chore
Keep unrelated changes in separate commits.
Commit only after tests relevant to the change pass.

Database Migrations

Schema source of truth: packages/store/src/schema.ts (drizzle-orm).
Migrations live at packages/store/drizzle/ and are applied automatically at gateway boot via runMigrations() (tracked in the drizzle.__drizzle_migrations table).
To change schema: edit schema.ts, then from packages/store/:
```
DATABASE_URL=... npx drizzle-kit generate --name <short_desc>
```
Review the generated SQL, commit schema.ts + drizzle/000N_*.sql + drizzle/meta/ together.
Never apply schema changes by hand-running psql against dev/prod. Manual SQL bypasses the migration tracker, so the next boot will try to re-apply and fail. If you must hotfix prod, also insert a matching row into drizzle.__drizzle_migrations so the runner stays in sync.
drizzle/_legacy/ holds pre-rebaseline SQL for historical reference only — do not edit.

Read the full file on GitHub · 59 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.

2mo ago First seen · 59 lines · 549 tokens per session scan A b6165b6d653c

Subscribe to this mod's changes

openhermit AGENTS.md is an instructions file published in the GitHub repository HCF-STUDIOS/openhermit (90 stars, last pushed 3d ago), licensed MIT. It adds 549 tokens to every session, about $0.0022 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.

agent-framework agent-infrastructure agent-orchestration agent-platform ai-agents multi-agent-systems

openhermit AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
openhermit AGENTS.mdHCF-STUDIOS/openhermit	Instructions file	90	3d ago	MIT	A	549	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

openhermit: Instructions file for Codex