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 AtlasOmnia/hermes-custom-pack --skill hermes-nightly-self-check-decisionsgit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packWrote 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/atlasomnia/hermes-custom-pack/hermes-nightly-self-check-decisions)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/hermes-nightly-self-check-decisions"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/hermes-nightly-self-check-decisions/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/atlasomnia/hermes-custom-pack/hermes-nightly-self-check-decisions"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/hermes-nightly-self-check-decisions.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.00030 | $0.00411 |
| Opus 5 | $0.00015 | $0.00205 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
hermes-nightly-self-check-decisions 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 12d 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.
This is a copy
100% identical to hermes-nightly-self-check-decisions — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Hermes Nightly Self-Check — Decisions Log
Purpose: Record decisions made from hermes-nightly-self-check findings so behavior is consistent across sessions.
How to record
Each entry captures one finding and the decision it produced. Use this format:
### YYYY-MM-DD — Short issue title (Issue #N)
- Issue: What the self-check flagged — the symptom, where it came from, and why it happened.
- Decision: The rule or fix chosen, stated so a future session can apply it without re-litigating.
Rules:
- One entry per finding; append chronologically under Decision history.
- Write the decision as an executable rule (what to do), not a description of what was done.
- If the finding is resolved by a change to config, skills, or process, note where that change lives so the next check can verify it.
- Do not record credentials, tokens, or private paths in the log — reference locations by role (for example "the primary model endpoint" or "the profile config") instead.
- If the same class of finding recurs, the decision should tighten the check or the rule, not just repeat the note.
Decision history
Starter template (Example #1)
- Issue: Nightly check flagged a mismatch between two config locations for the same setting.
- Decision: Keep one location canonical; document the relationship so future checks do not flag it as a conflict.
Setup flow (Example #2)
- Issue: A tool call failed because an argument was passed as null.
- Decision: Always specify an explicit value; never pass null or omit the argument. Default to the safest explicit value when unsure.
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.
- 12d ago First seen · 41 lines · 30 tokens per session scan A 629e5a6370b2
hermes-nightly-self-check-decisions is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (56 stars, last pushed 28d ago), licensed MIT. It adds 30 tokens to every session and 411 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hermes-nightly-self-check-decisions, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-dreaming-agnostic
Memory-agnostic background consolidation — reviews sessions, scores candidates, promotes durable insights to the active memory backend (built-in MEMORY.md or Holographic). Three-phase (Light/Deep/Condensation/REM). Run via cron or manually.
agent-dreaming
DEPRECATED — use agent-dreaming-agnostic instead. Background memory consolidation for built-in MEMORY.md only.
hermes-context-optimization
Use this when the user asks about Hermes prompt/context size, “hello” startup cost, compression behavior, memory/profile bloat, tool-schema overhead, skill loading, session-store/search-index storage, or multimodal/visual-context approaches such as Snapcompact.
hermes-mnemosyne
Mnemosyne is Hermes' primary local-first memory engine — SQLite with vector + FTS5 hybrid search, 19+ tools, auto-consolidation, and a standalone CLI. It's a pip-installed plugin (not a built-in toolset) discovered via $HERMESHOME/plugins/mnemosyne/.
hermes-session-maintenance
Use this skill when the user asks about pruning Hermes sessions, session retention, session DB size, hermes sessions prune, sessions.autoprune, sessions.retentiondays, session export/backup, or whether old conversations should be capped.
hermes-nightly-self-check-decisions
Purpose: Record decisions made from hermes-nightly-self-check findings so behavior is consistent across sessions.