Tholem-Hermes-Kit: Instructions file for Codex

AGENTS.md

Tholem-Hermes-Kit AGENTS.md is an instructions file for Codex, OpenCode from Tholem-AI/Tholem-Hermes-Kit. It costs 1,566 tokens per session, scanned A, original, MIT.

A project instruction file named AGENTS.md for Tholem Hermes Kit. It sets rules for approvals, safety, project documents, and the agent's working directory.

In plain words
What is it for?
For projects using Hermes that need governance, lifecycle rules, and quality checks applied during work.
Why use it?
It gives the agent consistent operating rules and prevents it from taking high-impact actions without approval or using outdated project guidance.

Instructions file for CodexOpenCode

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

This is Tholem-AI/Tholem-Hermes-Kit's own configuration. It tells Codex and OpenCode how to work on Tholem-Hermes-Kit 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 Tholem-Hermes-Kit configures →

Reuse

Borrowing it

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

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 Tholem-Hermes-Kit AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tholem-ai/tholem-hermes-kit/agents-md/github.svg)](https://agentmods.dev/instructions/tholem-ai/tholem-hermes-kit/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/tholem-ai/tholem-hermes-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/tholem-ai/tholem-hermes-kit/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 Tholem-Hermes-Kit AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tholem-ai/tholem-hermes-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/tholem-ai/tholem-hermes-kit/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,566 This file is loaded in full into every session.
When invoked 1,566 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.01566 $0.01566
Opus 5.5 $0.00626 $0.00626
Sonnet 5.5 $0.00313 $0.00313
Haiku 4.5 $0.00157 $0.00157

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

Security

Grade A, and why

Tholem-Hermes-Kit 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 · 107 lines

How it starts

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

Tholem Hermes Kit — System Instructions

This file defines always-on governance, execution lifecycle, safety, quality, and project-constraint policy for the Tholem Hermes Kit.

Copy this file to your project root. Hermes loads AGENTS.md automatically when the project root is the working directory (CWD).

Important: Hermes does NOT walk parent directories for AGENTS.md. It only looks in the current working directory. If you cd into a subdirectory, AGENTS.md will not be found. Use hermes config set terminal.cwd '/path/to/project' or start Hermes from the project root.

Governance (always-on)

  1. Require explicit user approval before high-impact actions: architecture changes, structural moves/renames, stack changes, or git writes.
  2. Escalate contradictions across runtime rules, roadmap, manifest, and migration runbook before continuing.
  3. Keep runtime artifacts operational-only. Move tutorials, long examples, and narrative rationale to docs/.
  4. Keep ROADMAP.md and relevant docs aligned with actual implementation state.
  5. Do not reactivate deprecated workflow artifacts (e.g., legacy task or memory archive files) as active execution targets unless explicitly approved by the user.

Execution lifecycle (RIPER)

  1. Follow RIPER sequencing for non-trivial work: Research -> Plan (with innovate checkpoint as needed) -> Execute -> Review.
  2. Treat innovate as a planning checkpoint, not a standalone mandatory phase.
  3. Use ROADMAP.md as the canonical active lifecycle surface.
  4. Use the riper-orchestrator skill to coordinate full RIPER phase handoffs.
  5. Agents may move work to Ready for Review but must not mark final completion unless both conditions are met:
    • explicit user confirmation, and
    • validation evidence required by the quality policy below.
  6. Significant phase transitions require concise handoff summaries with: what changed, why, impact on next actions, and responsible owner.
  7. Task and handoff updates must include concise evidence tied to actual repo changes.
  8. When execution changes project structure materially, keep docs/File-Structure-Reference.md aligned.

Read the full file on GitHub · 107 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. 2mo ago First seen · 107 lines · 1,566 tokens per session scan A 979e6491ede3

Subscribe to this mod's changes

Tholem-Hermes-Kit AGENTS.md is an instructions file published in the GitHub repository Tholem-AI/Tholem-Hermes-Kit (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,566 tokens to every session, about $0.0063 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-31.

Related

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).

microsoft/vscode · 9,715 tokens

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens