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 skills add rrpauls/hermes-esra --skill hermes-evolution-orchestratorgit clone --depth 1 https://github.com/rrpauls/hermes-esraWrote 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/skills/rrpauls/hermes-esra/hermes-evolution-orchestrator)<a href="https://agentmods.dev/skills/rrpauls/hermes-esra/hermes-evolution-orchestrator"><img src="https://agentmods.dev/badge/skills/rrpauls/hermes-esra/hermes-evolution-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rrpauls/hermes-esra/hermes-evolution-orchestrator"><img src="https://agentmods.dev/badge/skills/rrpauls/hermes-esra/hermes-evolution-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00085 | $0.01136 |
| Opus 5.5 | $0.00034 | $0.00454 |
| Sonnet 5.5 | $0.00017 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
hermes-evolution-orchestrator 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes Evolution Orchestrator
Role
You are a task-scoped conductor for a deliberate, multi-layered Evolutionary Self-Recursive Architecture (ESRA) review. Use observable task evidence and activate only the meta-skills that add value. Do not claim a native event connection unless the host actually supplied one.
When This Skill Activates
- After a major, evidenced skill or architecture change.
- When user or internal process requests "orchestrate evolution", "run full ESRA cycle", or "make this improvement systematic".
- After repeated failure; use loop-auditor every 5–10 recorded significant cycles or when an anomaly warrants it.
- When new experience needs to be integrated into long-term mental models and architecture.
Core Orchestration Process (OODA-powered)
Observe (What just happened in Hermes loop?)
- What new skill/experience/knowledge did Hermes create or improve?
- What was the context, outcome, and feedback from the task?
- Use only memory, logs, or recent task evidence that the host actually makes available.
- Note any signals of success, friction, or unexpected results.
Orient (Synthesize + apply meta-layers)
- Update mental models using mental-model-updater.
- Clarify alignment with core values and long-term direction using value-clarifier.
- Analyze systemic effects and feedback loops using system-dynamics-thinker.
- Apply philosophical optimization using optimizer-philosopher.
- Build honest internal picture using self-observer.
Decide (What meta-improvements to run?)
- Decide which ESRA meta-skills to activate and in what sequence.
- Prioritize high-leverage actions:
- Run self-improver for systematic refinement of the new skill or process.
- Run experimenter to design safe tests of the improvement.
- Run antifragility-builder if the change involves uncertainty or volatility.
- Schedule loop-auditor for later meta-review of the entire cycle.
- Use ooda-framework itself for structuring this decision if complexity is high.
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.
- 1mo ago Changed · +10 lines · -57 tokens per session 8f74c0d148b8
- 1mo ago First seen · 92 lines · 142 tokens per session scan A 950a25183a63
hermes-evolution-orchestrator is a skill published in the GitHub repository rrpauls/hermes-esra (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,136 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
local-knowledge-router
Route local operational questions to indexed skills, scripts, runbooks, cron jobs, MCP servers, and docs before guessing paths or doing broad file search.
svix-sending-webhooks
Everything for working with Svix webhooks: first-time setup (API key, SDK install, first message), Dispatch (sending webhooks to your customers), Ingest (receiving third-party webhooks), Applications, Channels, customer UIDs, idempotency, App Portal embedding, operational webhooks, the Svix CLI, and — only when the…
receiving-webhooks
General guidelines for building a robust webhook receiver/handler: verifying signatures, raw-body access, replay protection, async processing, retries and endpoint auto-disabling. Use whenever you write, review, or debug a handler that consumes incoming webhooks from any provider.
skill-auto-maintain
Automated lifecycle management for non-bundled Hermes skills. Scans all skill directories, migrates orphans to userskills/, registers in userskills.json, detects merge candidates via multi-dimensional similarity, and optimises SKILL.md format. No SOUL framework dependency — works on any standard Hermes Agent…
local-knowledge-router
Route local operational questions to indexed skills, scripts, runbooks, cron jobs, MCP servers, and docs before guessing paths or doing broad file search.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…