Borrowing it
Nothing to install: this file belongs to shan8851/hermes-console. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shan8851/hermes-console/main/AGENTS.mdgit clone --depth 1 https://github.com/shan8851/hermes-consoleWrote 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/shan8851/hermes-console/agents-md)<a href="https://agentmods.dev/instructions/shan8851/hermes-console/agents-md"><img src="https://agentmods.dev/badge/instructions/shan8851/hermes-console/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.1 | $0.00534 | $0.00534 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
hermes-console 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 6d 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.
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 — Hermes Console
What this is
Hermes Console is a local-first monorepo for inspecting Hermes Agent setups.
Current workspace shape:
packages/runtimefor pure schemas, types, and domain helpersapps/apifor filesystem reads, CLI diagnostics, and the local HTTP boundaryapps/webfor the Vite React UI
It is:
- Hermes-native
- read-mostly at launch
- visibility-first, not chat-first
- intended as a clean, focused product
Product priorities
When working in this repo, optimise for:
- legibility
- calm operator UX
- simple local setup
- modular code structure
- strong naming and obvious file organisation
- small, testable units
Non-goals for v1
Do not let the repo drift into:
- generic multi-agent platform abstractions
- terminal emulator work
- chat-client parity work
- full file manager/editor scope
- enterprise auth / RBAC theatre
- Shan-specific bespoke workflow surfaces as core primitives
Code structure expectations
- Prefer small composable components over giant page files.
- Keep reader/parsing logic in
apps/apiorpackages/runtime, never inapps/web. - Keep
packages/runtimepure and framework-agnostic. - Create explicit internal types for each source family.
- Prefer strong names that explain intent:
CronJobsTable,readSkillsIndex,formatMemoryUsage. - Keep file and folder structure obvious and domain-led.
- Avoid catch-all
utilsdumping grounds when a domain module is clearer.
Testing expectations
Add unit tests for:
- readers
- parsers
- normalizers
- schedule / usage / warning calculations
- any non-trivial UI state helpers
If logic is important enough to deserve a helper, it usually deserves a test.
Local config expectations
Expect .env.local for local overrides.
Planned important env vars:
HERMES_CONSOLE_HERMES_DIRHERMES_CONSOLE_WORKSPACE_DIRPORT
Default assumption is a standard Hermes setup under ~/.hermes.
UX expectations
- Dark-first.
- Giles-style information clarity.
- Hermes-style branding and accents.
- Dense but breathable layouts.
- Make important state obvious in one screen when possible.
- Avoid noisy dashboards and fake enterprise complexity.
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.
- 6d ago First seen · 93 lines · 534 tokens per session scan A f4a30165eeb0
hermes-console AGENTS.md is an instructions file published in the GitHub repository shan8851/hermes-console (10 stars, last pushed 3mo ago), licensed MIT. It adds 534 tokens to every session, about $0.0027 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.