# Omh Agent Instructions

[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-agent-instructions -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-agent-instructions -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-agent-instructions -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-agent-instructions -g -a gemini-cli -y`

## Description

[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or marked unverified and no counts that drift. Use when the user says: agent-instructions, agents.md, claude.md, gemini.md, copilot-instructions.md, .cursorrules, cursor rules, cursor rule.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Agent Instructions

This is an OMH `agent-instructions` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`agent-instructions` exists because the file every handoff target reads first had no owner: `rules-distill` extracts rule candidates, `codebase-onboarding` builds a human reading path, and `context` aligns terminology, and each reads that file without writing it.

## First Steps

- List every instruction file and which agent reads it before proposing a section.
- Run or ask for the observed run of each command before marking it verified.

## Do Not Use When

- The ask is distilling repeated lessons into reviewed rule candidates; use `omh-rules-distill`.
- The ask is a reading path through the codebase for a new engineer; use `omh-codebase-onboarding`.
- The ask is project terminology alignment -- reviewing the terms this project uses and correcting inconsistent vocabulary; use `ulw-context`.
- The ask is user-facing product documentation; use `omh-docs`.

## Examples

Good example:

- Prompt: update our CLAUDE.md
- Expected behavior: Inventory the instruction files, run or collect each build and test command, mark each verified or unverified, and replace only the marked region with the commands, the generated-file map, the gates, and the costed pitfalls, refusing any count or line number.
- Why: An instruction file that states an unrun command or a stale count sends every later agent the wrong way.

Bad example:

- Prompt: add that the suite has 4,100 tests and the router is at line 212 of chat.py
- Expected behavior: Refuse both values, and write the command that counts the tests and the symbol that locates the router instead.
- Why: Both numbers were already wrong by the next merge.

## Completion Checklist

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-agent-instructions/SKILL.md