docs(readme): add hermes-telemetry to Community section

[hashbender]

What & why

Adds a one-line entry under Community for hermes-telemetry, an MIT,
runtime-integrated plugin (installed into ~/.hermes/plugins/) that hooks into
the model-call pipeline to record per-session and per-cron token, cost, and
latency into local SQLite — and, unlike report-after-the-fact dashboards, can
pause a cron run before it breaches a soft/hard budget cap.

The gap it fills

Observability tools already report what was spent. What multiple users have
asked for is a guardrail that stops spend before it happens, for unattended
(cron/gateway) operation:

• Cron jobs and agent dispatches burn provider credits without user consent or budget cap NousResearch/hermes-agent#23419 — cron jobs burn provider credits with no budget cap (~$20/day incident)
• [Feature]: Configurable daily/monthly hard budget cap for unattended operation NousResearch/hermes-agent#26382 — request for a configurable daily/monthly hard budget cap that gates
  the model call, returning a structured error on breach

Evidence the pain is real: NousResearch#44771 (91M-token runaway loop), NousResearch#45782
(unexpected $145 in API costs), NousResearch#45783 (credit spikes on session resume).

hermes-telemetry implements exactly this enforcement path via the plugin
hooks, plus /stats and /budget, with OpenRouter pricing auto-synced.

Relationship to native work

This complements — it does not replace — the first-class telemetry effort in
NousResearch#51714 and the budget-enforcement hook proposal in NousResearch#52648. It's an opt-in,
available-today option for users who need a spend guardrail now.

Links

• Plugin repo: https://github.com/nujovich/hermes-telemetry (MIT)
• Install: hermes plugins install nujovich/hermes-telemetry

How to test

Markdown-only change — verify the rendered Community section.

Platforms

N/A (docs).

---

Mirror-of: NousResearch#56441
NousResearch#56441

[tenki-reviewer]

Review Complete
No issues found!

Risk: 🟢 Low (0/100) — no findings · 3 LOC across 1 file

---

PR #373 contains only a documentation change to README.md. No code, logic, security, or configuration changes are present.

Files Reviewed (1 files)

README.md