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 lifeoshooksgit 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/lifeoshooks)<a href="https://agentmods.dev/skills/danielmiessler/lifeos/lifeoshooks"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/lifeoshooks/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/lifeoshooks"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/lifeoshooks.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.00114 | $0.02975 |
| Opus 5.5 | $0.00046 | $0.01190 |
| Sonnet 5.5 | $0.00023 | $0.00595 |
| Haiku 4.5 | $0.00011 | $0.00298 |
Grade A, and why
LifeOSHooks 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 today.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LifeOSHooks
Diagnoses the LifeOS function-hook plugin, the in-process half of the hook system (one hooks module Claude Code's function-hook runtime loads once per interactive session; the command hooks under hooks/ remain the out-of-process half): whether it is armed, why a line or banner did or did not draw, and keeping its types and pure-core copies current. State of record: LIFEOS/FUNCTIONHOOKS/ISA.md (maintainer-side; the ISA does not ship).
Ideal State
- A status answer ("is the plugin loaded and working") says armed or not, on which build, and names its evidence: this session's stamp in
MEMORY/STATE/function-hooks/<session>.json(the command hooks read it to go quiet on the lines the plugin draws),hooks/lib/build.ts, and for a headless check the probe's debug log. A verdict with no evidence fails. - The check holds the plugin to its standing properties: armed in every interactive session on the declared build, and in a headless session (
-p, the SDK, Relay) every hook a passthrough with nothing drawn. - A "why did or didn't this draw" answer names the surface that owns the line (§ References) and the cause it found; a guess is labelled as one.
- After a Claude Code update,
.claude/types/claude-code.d.tswas written by the running build,hooks/lib/build.tsnames that build, and the typecheck and tests pass; the answer names the old and the new build. claude plugin validate <plugin dir>passes; its hooked-events list matches the ISA's closed criteria (/icchecks this).- The pure-core copies under
hooks/lib/equal their sources (tests/parity.test.ts; source tree only, not in the public release payload).
Anti-criteria
- No diagnostic
$.ui.logline is ever added to the live module, not even for one probe run. In any session that loads the edited module (§ Gotchas, reload), every$.ui.logline prints into the principal's transcript: one temporary diagnostic line, printed once per tool call, filled the screen (2026-10-02). Probe in a copy run withclaude --plugin-dir <copy>and--debug-file, or put the diagnostic inpushEvent, which only reaches the events log. - A report never tells the principal a save already reloaded an open session; a check of a change in a live session starts with
/reload-plugins(2026-10-11: a pane removed on disk kept drawing its old text in open sessions until a reload).
What ships with it
22 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.
- .claude/types/lifeos-tools.d.ts 1.2 KB runs code
- assets/chime.wav 4.7 KB
- hooks/hooks.json 38 B
- hooks/lib/board-view.ts 17 KB runs code
- hooks/lib/build.ts 1.2 KB runs code
- hooks/lib/context-reduction-core.ts 4.2 KB runs code
- hooks/lib/egress-shapes.ts 13 KB runs code
- hooks/lib/glyph-core.ts 8.2 KB runs code
- hooks/lib/injection-shapes.ts 5.7 KB runs code
- hooks/lib/motion-view.ts 15 KB runs code
- hooks/lib/outbound-shapes.ts 63 KB runs code
- hooks/lib/panes-view.ts 2.4 KB runs code
- hooks/lib/route-label.ts 18 KB runs code
- hooks/lib/shell-view.ts 2.4 KB runs code
- hooks/lib/subagent-sandbox-wrap.ts 1.7 KB runs code
- hooks/lib/system-surfaces.ts 6.2 KB runs code
- hooks/LifeOSHooks.ts 124 KB runs code
- References/ModuleGotchas.md 3.9 KB
- scripts/MakeChime.ts 1.8 KB runs code
- scripts/SyncCores.ts 2.4 KB runs code
- Setup.md 3.3 KB
- tsconfig.json 341 B
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.
- today First seen · 87 lines · 114 tokens per session scan A 825eb328076f
LifeOSHooks is a skill published in the GitHub repository danielmiessler/LifeOS (19,616 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 2,975 once invoked, about $0.0005 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-10-28.
Other skills, from other repositories
aster-fix-workflow
Pipe aster review findings into aster fix to generate and apply patches safely, using review --json, fix --findings-json, dry-run inspection, --apply, and permission gating. Use when asked to auto-fix review findings, apply aster's suggested edits, or build a review-then-fix pipeline.
lsp-navigation
Semantic code navigation and fast error checks with the lspdiagnostics, lspreferences, and lspdefinitions tools. Use instead of a full build to check whether an edit broke something, or to find real usages of a symbol.
build-triage
Reading build, test, and compiler failures fast. Use when a build or test command fails, hangs, times out, or produces a wall of output.
debug-systematically
Finding the cause of a bug instead of guessing at fixes. Use when something fails and the cause is not obvious, when a fix did not work, or when the user reports a bug without a clear trigger.
harness-audit
A codebase scan for five common weaknesses in the setup used to guide and check an AI agent. It produces a diagnostic report and can optionally fix the problems it finds.
harness-retro
Retrospective on completed harness tasks. Analyzes run data (scores, eval reports, changelogs) to identify convergence issues, bottleneck dimensions, repeated work, and cost inefficiency. Generates concrete prompt/rubric improvements. Optionally archives completed tasks. Standalone archive mode available — skip…