LifeOS is an AI-assisted personal operating system that records a person’s goals, values, context, and current situation to help move them toward a desired future state. It supports work such as building applications, starting businesses, and creative projects. Its catalogue entries extend the system through skills, hooks, agents, and commands.
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 danielmiessler/LifeOS --skill hermesgit clone --depth 1 https://github.com/danielmiessler/LifeOSWrote 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/danielmiessler/lifeos/hermes)<a href="https://agentmods.dev/skills/danielmiessler/lifeos/hermes"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/hermes/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/danielmiessler/lifeos/hermes"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/hermes.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.00000 | $0.01777 |
| Opus 5.5 | $0.00000 | $0.00711 |
| Sonnet 5.5 | $0.00000 | $0.00355 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
Hermes 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes
Observability over a mounted Hermes sidecar. The sidecar keeps its own records (session store, cron execution history, error logs, guard audit trail), and this skill turns them into answers: is it healthy, what failed and why, and exactly what happened inside one task.
Everything runs against the live install at $HERMES_HOME (default ~/.hermes) through deterministic tools in LIFEOS/HERMES/: Observe.ts status|failures|sessions|trace (the aggregator: sessions, failure classes, end-to-end traces), Health.ts (process health: up/degraded/flapping/down/absent, per-channel state), LogAnalysis.ts [--days N] (guard audit trail: hot rules, retry loops, taint findings) and Mount.ts --check (identity/config drift, report-only). Diagnosis mutates nothing: no config writes, no restarts, no cron edits. The Update intent is the one place the sidecar changes. Fixes route through Policy.ts + Mount.ts (the mount owns config), never hand-edits.
Ideal State
- Every answer about the sidecar is grounded in its own records through the
LIFEOS/HERMES/tools, and success is judged from traces, never from an execution status. - Whether sessions actually load the LifeOS soul is always answered, and a blocked soul leads any report it appears in.
- Every failure or fix names its owner (
Policy.tsor soul sources plus a re-mount, the approval allowlist, or upstream Hermes) and the sidecar is never mutated by a diagnosis.
Intent Routing
| Intent | Trigger | File |
|---|---|---|
| Status | "hermes status", "is hermes healthy", "is the sidecar running LifeOS" | Intents/Status.md |
| Triage | "why do hermes tasks fail", "hermes failures", "triage hermes" | Intents/Triage.md |
| Trace | "trace that task", "what happened to my message", "show me that hermes session" | Intents/Trace.md |
| Update | "update hermes", "upgrade hermes", "is hermes up to date" | Intents/Update.md |
| File | Read when |
|---|---|
Setup.md |
first-time setup: installing and mounting the optional sidecar the skill observes, and a read-only check |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 76 lines · 0 tokens per session scan A fe37889aacdd
Hermes is a skill published in the GitHub repository danielmiessler/LifeOS (19,637 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,777 tokens. 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-10-28.
Other skills, from other repositories
material-ui-nextjs
Integrates Material UI with Next.js App and Pages routers using @mui/material-nextjs, Emotion cache providers, next/font, CSS layers with Tailwind/CSS Modules, Link component prop patterns, CSS theme variables SSR notes, and App Router useSearchParams + Suspense. Use when setting up or debugging MUI in a Next.js app.
benchmark-workflow
Xberg extraction benchmarks: running, quality scoring, fixtures, ground truth. Use for the Benchmarks workflow or benchmark-harness work.
recipe-diagnose
Investigate problem, verify findings, and derive solutions.
authoring-error-tracking-alerts
Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing…
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.
prompt-debugging
Figure out why a prompt isn't working and fix it — diagnose the actual failure (ambiguity, missing context, wrong format, conflicting instructions) instead of randomly rewording. Use when asked why isn't my prompt working, the AI keeps ignoring my instructions, my prompt gives inconsistent results, or how do I fix…