nujovichChallenge Entry for the Hermes Agent Challenge ๐ What Problem Does This Solve? AI agent...
Challenge Entry for the Hermes Agent Challenge
AI agent deployments often suffer from two critical blind spots:
hermes-telemetry solves both by giving you real-time observability and automatic budget enforcement for Hermes Agent.
Every production AI system needs observability and cost control. This isn't just a nice-to-have โ it's essential infrastructure.
Before this plugin, Hermes users had no way to:
Now they can manage their AI spend like a modern SaaS โ with dashboards, alerts, and automatic circuit breakers.
Captures actual token counts and costs returned by providers like OpenRouter, OpenAI, and Anthropic. No guesswork.
/stats โ session performance, tool usage, cost breakdowns/stats cron week โ cron job cost comparison across time/stats providers โ which providers return real vs estimated data/budget โ current spending vs limits with visual indicatorsPure observability layer โ captures everything through hooks without affecting model behavior or adding latency.
/stats)
/budget)
/stats cron week)
/stats providers)
I tested the plugin with three different models to validate pricing accuracy and budget enforcement:
| Model | Cost per Test Run | Budget Behavior |
|---|---|---|
owl-alpha (free) |
$0.00 | No limits triggered |
claude-sonnet-4-6 |
$0.31 | Soft warning at $0.001 limit |
claude-opus-4-7 |
$2.23 | Hard pause enforced โ |
Budget enforcement works. When I set a $0.001 daily limit and ran a cron job, it correctly paused at $0.18 spending. When I raised the limit to $2.00, jobs resumed normally.
Real provider data. OpenRouter returned actual token counts (Est% = 0%), not estimates. The plugin correctly captured and priced these.
on_session_start โ pre_api_request โ โ
post_api_request โ post_tool_call
โ
โผ
[capture usage]
โ
โผ
pre_llm_call (budget check) โ pre_tool_call (tool gate) โ SQLite storage
Works with any provider that follows the Hermes Agent provider interface:
This isn't a demo โ it's production infrastructure. The plugin includes:
/budget set without restart
cd ~/.hermes/plugins
git clone https://github.com/nujovich/hermes-telemetry.git
# Add 'hermes-telemetry' to plugins.enabled in config.yaml
# Restart gateway: hermes gateway restart
# Set daily budget
hermes> /budget set global daily 5.00
# Check status
hermes> /budget
# Session stats
hermes> /stats
# Cron job breakdown
hermes> /stats cron week
# Provider analysis
hermes> /stats providers
That's it. The plugin immediately starts capturing usage data for all sessions and cron jobs.
This plugin solves a universal need in AI systems โ cost visibility and control. Every Hermes Agent deployment, from personal automation to enterprise cron jobs, benefits from this infrastructure.
It's not just useful, it's essential. Without budget controls, a misconfigured cron job with an expensive model can cost hundreds of dollars overnight. This plugin prevents that.
Real-world tested. I built, deployed, and validated this with actual usage data across multiple providers and models. It's not a concept โ it's working infrastructure that saves money and provides operational insight.
Community impact. This sets a standard for observability in the Hermes ecosystem. Other plugin authors can build on these patterns, and users get immediate operational confidence.
I'm Nadia Ujovich.
I understand the operational challenges of running AI systems at scale, and I built this plugin to solve the observability gap I see in every deployment.
This plugin makes Hermes Agent production-ready for cost-conscious deployments. It's the infrastructure piece that every serious AI system needs, but few teams build themselves.
Give your agents the observability they deserve. Try hermes-telemetry today.
Made with โ for the Hermes Agent ecosystem