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 visualizegit 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/visualize)<a href="https://agentmods.dev/skills/danielmiessler/lifeos/visualize"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/visualize/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/visualize"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/visualize.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.00197 | $0.01801 |
| Opus 5.5 | $0.00079 | $0.00720 |
| Sonnet 5.5 | $0.00039 | $0.00360 |
| Haiku 4.5 | $0.00020 | $0.00180 |
Grade A, and why
Visualize 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visualize
Contents: Ideal State · Intent Routing · Data & Config · Split of work · Gotchas · Examples
Points at a project, repo, directory or ISA and leaves the principal understanding how it works: a concise ASCII map in the console and a designed HTML explanation saved next to the code. The purpose is that nothing runs in production that nobody understands.
Points at a physical plan (a gear setup, a rig, a room, a purchase list) and leaves the principal seeing it: a to-scale top-down drawing with the cost split, the full order and the open decisions, every fact quoted from the plan document.
Anything else (an idea, a comparison, a dataset, a timeline, a process) becomes one hand-built concept page with a short console summary. The skill never declines.
Ideal State
- Whatever is named gets visualized through the route that fits it (system map, physical plan or concept page), never declined and never squeezed into the wrong route.
- Every fact on a page says where it came from (a
fileorfile:line, a verbatim plan quote, a URL,computed, the principal's words orgeneral knowledge), and anything unconfirmed is labelled as such rather than stated. - The console summary alone tells the principal what the thing is and the one thing worth acting on, and the page holds the full picture, looked at in a real renderer before delivery.
- The subject is only read: the page (and a plan's model under USER) are the only writes, and no secret value lands on any page.
Intent Routing
| Intent | Trigger | File |
|---|---|---|
| Visualize | "visualize" on code, "how does X work", "map this system", "explain this architecture" | Intents/Visualize.md |
| Plan | "visualize" on a physical thing: "visualize my drum/studio/desk plan", "lay out my setup", "draw my rig", "show me my order" | Intents/Plan.md |
| Concept | "visualize" on anything that is neither code nor a physical plan: an idea, a scientific question, a comparison, a dataset, a timeline, a process | Intents/Concept.md |
What ships with it
7 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.
- yesterday First seen · 101 lines · 197 tokens per session scan A 62d60dc623b6
Visualize is a skill published in the GitHub repository danielmiessler/LifeOS (19,631 stars, last pushed today), licensed MIT. It adds 197 tokens to every session and 1,801 once invoked, about $0.0008 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
build-product-and-tool-interfaces
A guide for designing and building complete interfaces for products and professional tools that people use repeatedly to change objects and reach checkable results. It covers workbenches, task workflows, editing tools, analysis tools, monitoring consoles, and file or asset processors.
dashboard
Update the agent's Control Center. Use when the user says "update my Control Center", "update my dashboard", "redesign my home", or "/dashboard".
user-research-synthesis
Analiza y sintetiza hallazgos de investigación de usuarios en insights estructurados y accionables. Úsalo cuando te proporcionen datos de investigación de usuarios, transcripciones de entrevistas, resultados de encuestas o feedback de usuarios que necesiten ser analizados y resumidos. Produce una síntesis temática con…
prototype
A skill for building a temporary prototype to answer one focused design or logic question. It either creates an interactive state-model demo or several switchable user-interface variations, depending on the question.
recipe-front-design
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval.
pages_guide
Guidance for making interactive pages beside the chat with pagecreate, pageupdate and pageread.