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-overnight-autonomygit 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-overnight-autonomy)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/hermes-overnight-autonomy"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/hermes-overnight-autonomy/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-overnight-autonomy"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/hermes-overnight-autonomy.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.00017 | $0.03035 |
| Opus 5.5 | $0.00007 | $0.01214 |
| Sonnet 5.5 | $0.00003 | $0.00607 |
| Haiku 4.5 | $0.00002 | $0.00303 |
Grade A, and why
hermes-overnight-autonomy 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.
This is a copy
100% identical to hermes-overnight-autonomy — 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes Overnight Autonomy
Use this skill when the user asks for Hermes projects to continue across the night, gateway restarts, worker failures, or 24/7 operation. The target is durable progress with bounded risk—not a tower of supervisors.
Architecture decision
Use Kanban as the durable execution kernel:
- SQLite-backed cards preserve task bodies, dependencies, claims, heartbeats, run history, comments, retries, and circuit-breaker state.
- The gateway-embedded dispatcher is the normal scheduler and stale-claim reclaimer.
- Each unattended card has an explicit runtime cap, retry budget, named assignee, workspace, and acceptance contract.
- A separate OS-supervised watchdog provides liveness and alerting when the gateway or dispatcher is unavailable.
- Recovery remains disabled during calibration. Do not add a standalone Kanban daemon against the same board database or multiple competing relaunchers.
Kanban solves durable task lifecycle and dead-worker redispatch; it does not prove meaningful progress, resume in-memory reasoning, judge code quality, substitute models automatically, or survive total gateway loss by itself.
Rollout stages
Stage 0 — Read-only baseline
Before any mutation, collect:
- Hermes version and live profile roster; never invent assignee names.
- Gateway service state, launchd/systemd ownership, PID, and ticker/cron health.
- Kanban board list, dispatcher configuration, board diagnostics, and current running tasks.
- Existing watchdogs, rescue registries, cron jobs, launchers, and service labels; pause/avoid overlapping writers rather than creating duplicates.
- Exact checkout/file ownership for every intended write surface.
Use the smallest existing empty board for a pilot when appropriate; do not create a second board merely to prove the lifecycle.
Stage 1 — Disposable lifecycle pilot
Create one harmless card with:
- a real existing assignee;
workspace=scratchunless repository work is explicitly required;- a short runtime cap and one retry maximum;
- explicit instructions to show state, heartbeat, comment, and complete;
- no repository, credential, external-service, or configuration access.
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 First seen · 193 lines · 17 tokens per session scan A 0713f984107d
hermes-overnight-autonomy is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (73 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 3,035 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hermes-overnight-autonomy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
delegation-brief
Before delegatetask: brief the subagent, then verify it.
work-ledger
Multi-day or multi-session work: a ledger that survives.
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…
spec-driven-development
Turns an approved idea or ticket into spec, plan, and task files saved in the repo, then executes them one task at a time with a progress log. Use to write a spec, plan a feature, break work into tasks, or resume multi-session work.
ticket-writer
Interactive tool that writes a ticket of the right type (story, subtask, bug, epic, or initiative) with its own structure and quality checks, ready to paste into any tracker. Use when asked to write a ticket, draft a user story, file a bug, or scope an epic.
stakeholder-update-writer
Writes a stakeholder Slack or email update message. Use when the user wants to communicate project status, blockers, decisions, or release readiness to stakeholders.