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.
npx agentmods add instructions/przbadu/hermes-ui/agents-mdgit clone --depth 1 https://github.com/przbadu/hermes-uiWrote 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.
[](https://agentmods.dev/instructions/przbadu/hermes-ui/agents-md)<a href="https://agentmods.dev/instructions/przbadu/hermes-ui/agents-md"><img src="https://agentmods.dev/badge/instructions/przbadu/hermes-ui/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.01006 | $0.01006 |
| Opus 5 | $0.00503 | $0.00503 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
hermes-ui AGENTS.md scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. `curl -sf http://127.0.0.1:9119/api/status` confirms a gateway is reachable. Note its host and port. You will serve the UI from the gateway itself, so it must be one you can start or restart. How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Runbook for an AI agent (Hermes, Claude Code, and similar) to set up and run hermes-ui.
Follow the steps in order.
This uses the manual path only: build the bundle and serve it from the gateway.
For the full human-facing reference, see README.md.
What you are setting up
hermes-ui is a browser UI for a running Hermes gateway.
It has no backend of its own.
The gateway serves the built bundle, so the UI, REST, auth, and the WebSocket all share the gateway's origin.
The one hard rule
The UI MUST be served same-origin with the gateway.
The gateway rejects cross-origin browsers: CORS is locked to localhost, session cookies are SameSite=Lax, and the WebSocket closes foreign origins with close code 4403.
Serving the bundle from the gateway (the steps below) satisfies this automatically.
Do not host the bundle on a different origin and point it at the gateway; OAuth sign-in and the WebSocket will fail.
Preflight
Run these checks before changing anything.
bun --versionverifies the package manager and script runner. If it is missing, install it from https://bun.sh and stop if it cannot be installed.command -v hermesverifies the Hermes CLI that runs the gateway. If it is missing, the gateway is not installed here; ask the human where the gateway runs.curl -sf http://127.0.0.1:9119/api/statusconfirms a gateway is reachable. Note its host and port. You will serve the UI from the gateway itself, so it must be one you can start or restart.
Build
From the repo root:
cd app
bun install
bun run build
This produces app/dist/ containing index.html and an assets/ subdirectory.
The build is a single large bundle, so expect it to take a few seconds and be tens of MB.
Serve (manual)
Serve the built bundle FROM the gateway so everything is same-origin. Prefer the ready-made runner, from the repo root:
./bin/prod # builds if needed, then serves from the gateway
./bin/prod --port 9200 # extra args pass straight through to 'hermes serve'
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.
- 4d ago First seen · 93 lines · 1,006 tokens per session scan A f27c83a96fb4
hermes-ui AGENTS.md is an instructions file published in the GitHub repository przbadu/hermes-ui (111 stars, last pushed 16d ago), licensed MIT. It adds 1,006 tokens to every session, about $0.0050 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
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.
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.
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.
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).
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.