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/mudrii/hermesd/claude-mdgit clone --depth 1 https://github.com/mudrii/hermesdWrote 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/mudrii/hermesd/claude-md)<a href="https://agentmods.dev/instructions/mudrii/hermesd/claude-md"><img src="https://agentmods.dev/badge/instructions/mudrii/hermesd/claude-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.01331 | $0.01331 |
| Opus 5 | $0.00665 | $0.00665 |
| Sonnet 5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
hermesd CLAUDE.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 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.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Overview
hermesd is a standalone TUI monitoring dashboard for Hermes Agent. It reads data from ~/.hermes/ (SQLite DB, JSON/YAML config, log files, skill directories) and displays it in a live-updating Rich terminal interface.
Key constraint: hermesd is read-only — it must never write to ~/.hermes/ or import any hermes-agent code. It's installed and runs independently.
Build & Test
uv venv .venv --python 3.11
source .venv/bin/activate
uv sync --locked --all-extras --dev
uv run pytest tests/ -v -W error::ResourceWarning # full suite
uv run ruff check . # lint
uv run ruff format --check . # format check
uv run mypy hermesd # type check
uv run python -m compileall hermesd # compile check
uv run pip-audit # dependency audit
uv lock --check # lockfile freshness
uv build # package build
python -m venv /tmp/hermesd-wheel-smoke
/tmp/hermesd-wheel-smoke/bin/python -m pip install dist/hermesd-*.whl
/tmp/hermesd-wheel-smoke/bin/hermesd --version
/tmp/hermesd-wheel-smoke/bin/python -m hermesd --version
python -m venv /tmp/hermesd-sdist-smoke
/tmp/hermesd-sdist-smoke/bin/python -m pip install dist/hermesd-*.tar.gz
/tmp/hermesd-sdist-smoke/bin/hermesd --version
/tmp/hermesd-sdist-smoke/bin/python -m hermesd --version
uv run twine check dist/* # package metadata
hermesd # run the dashboard
hermesd --hermes-home /path # custom hermes home
hermesd --profile coding # opt-in profile-scoped runtime data
hermesd --snapshot # one-shot overview to stdout
hermesd --snapshot-panel 10 # one-shot detail snapshot in text mode
hermesd --snapshot-panel 0 # panel 10 alias matching the interactive shortcut
hermesd --snapshot-panel 12 # one-shot detail snapshot for any registered panel
hermesd --snapshot-format json # machine-readable full-state snapshot
hermesd --log-tail-bytes 8192 # cap per-refresh log reads for large files
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 · 98 lines · 1,331 tokens per session scan A 44a1b2a8bd28
hermesd CLAUDE.md is an instructions file published in the GitHub repository mudrii/hermesd (116 stars, last pushed 15d ago), licensed MIT. It adds 1,331 tokens to every session, about $0.0067 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-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.