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 vitalsgit 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/vitals)<a href="https://agentmods.dev/skills/danielmiessler/lifeos/vitals"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/vitals.svg" alt="Measured on agentmods" 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.00179 | $0.01223 |
| Opus 5 | $0.00089 | $0.00611 |
| Sonnet 5 | $0.00036 | $0.00245 |
| Haiku 4.5 | $0.00018 | $0.00122 |
Grade B, and why
Vitals scanned grade B with 2 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **`powermetrics` requires sudo and runs forever without `-n`.** It's the only accurate source of per-process energy and GPU power — keep it as the optional consent-gated leg in DeepDiagnosis. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://localhost:31337/notify \ 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.
Vitals
Read-only macOS performance inspection: a deterministic CLI gathers the numbers, Interpretation.md turns them into a diagnosis instead of a data dump.
Customization
Before executing, check for user customizations at:
~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Vitals/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
Voice Notification
When executing a workflow, do BOTH:
-
Send voice notification:
curl -s -X POST http://localhost:31337/notify \ -H "Content-Type: application/json" \ -d '{"message": "Running WORKFLOWNAME in Vitals"}' \ > /dev/null 2>&1 & -
Output text notification:
Running **WorkflowName** in **Vitals**...
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| HealthCheck | "how's my system", "check my mac", "system health" | Workflows/HealthCheck.md |
| FindCulprit | "mac is slow", "what's eating CPU/GPU/memory", "fans loud" | Workflows/FindCulprit.md |
| DeepDiagnosis | "full diagnosis", "deep check", chronic/recurring slowness | Workflows/DeepDiagnosis.md |
Interpretation reference (load with any workflow): Interpretation.md — thresholds, known-process table, diagnosis shape.
Quick Reference
bun ~/.claude/skills/Vitals/Tools/Vitals.ts check # fast snapshot (<1s)
bun ~/.claude/skills/Vitals/Tools/Vitals.ts hogs # live per-process CPU/energy (~3s)
bun ~/.claude/skills/Vitals/Tools/Vitals.ts full # everything (~4s)
# also: gpu · memory · disk · thermal · startup · --json · --top N
The tool is read-only by contract: it never kills, renices, unloads, or writes system state. Remediation is recommended to the operator, never executed by the skill.
Examples
Example 1: Something feels slow
User: "My Mac is dragging, what's going on?"
→ FindCulprit: run hogs + check + gpu
→ Cross-reference Interpretation.md (is the hog a known background process?)
→ Report: named culprit with two evidence classes, recommended action for approval
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.
- 3d ago First seen · 87 lines · 179 tokens per session scan B 9501a3fdc6ba
Vitals is a skill published in the GitHub repository danielmiessler/LifeOS (18,899 stars, last pushed 2d ago), licensed MIT. It adds 179 tokens to every session and 1,223 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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
Run, diagnose, or change Xberg extraction benchmarks, quality scoring, benchmark fixtures, artifact contracts, and independently sourced ground truth. Load for the Benchmarks workflow or benchmark-harness work, not ordinary unit tests.
verified-script-execution
Fallback workflow for reliable file creation and verification when automated code execution fails.
verify-success-after-unknown-error
Verify task completion by checking filesystem state when executecodesandbox or runshell return misleading unknown errors.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.
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…