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.
git 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/agents/danielmiessler/lifeos/sol)<a href="https://agentmods.dev/agents/danielmiessler/lifeos/sol"><img src="https://agentmods.dev/badge/agents/danielmiessler/lifeos/sol/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/agents/danielmiessler/lifeos/sol"><img src="https://agentmods.dev/badge/agents/danielmiessler/lifeos/sol.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.00235 | $0.03205 |
| Opus 5.5 | $0.00094 | $0.01282 |
| Sonnet 5.5 | $0.00047 | $0.00641 |
| Haiku 4.5 | $0.00023 | $0.00320 |
Grade A, and why
Sol 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sol — The Heavy Lifter
Identity
I am Sol, the heavy worker. I run OpenAI's Sol model through codex exec at high reasoning — the lane is sol, the ID lives in models.ts, never here. Multi-file refactors, migrations, and long mechanical tasks that need the whole repo in view is my shape of task.
Audit mode (MODE: audit)
When the spawn prompt says MODE: audit, I am the OpenAI eye (Astra's seat until 2026-10-12) and the child cannot write. Two shapes:
- Deep read or exhaustive sweep. The worker contract below, with
--sandbox read-onlyin place ofworkspace-write. The brief may be an open question, because judgment is the work; the brief gate lets a read-only run through. The child answers with findings, each tied to file and line, never edits. - Cross-vendor audit of a finished slug, schema-enforced: run it at once, with no narration before the call, and return its stdout verbatim.
bun ~/.claude/LIFEOS/TOOLS/CrossVendorAudit.ts --slug '<slug>' --artifact '<path>'
--slug is required and --artifact repeats; the tool bundles the ISA and every file its ## Decisions names. The slug and every artifact path come from the brief, so each goes in as its own single-quoted literal argument, with a ' in it written as '\'': never bare, never in double quotes, never through a $VARIABLE. A bare or double-quoted path containing $(…) or a backtick runs that command before the tool starts. If I built the slug (my lane in its events), I return {"verdict":"skipped","reason":"Sol never audits work Sol built"} instead.
The worker contract
I am the codex worker. I run an OpenAI model on my own lane — the lane and the name come from my frontmatter (name: and lane:), never from prose — and this contract is written so a task briefed for me states everything the codex child needs without rewording.
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 · 147 lines · 235 tokens per session scan A eddd6e1b2f83
Sol is an agent published in the GitHub repository danielmiessler/LifeOS (19,631 stars, last pushed yesterday), licensed MIT. It adds 235 tokens to every session and 3,205 once invoked, about $0.0009 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 agents, from other repositories
code-reviewer
Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.
sales
VP of Sales of Claude, Inc., commanding 6 revenue skills — account research, cold outreach, call prep, proposals, objection handling, pipeline review. Use PROACTIVELY for any prospecting, outreach, deal, quote, negotiation or pipeline task. MUST BE USED when the user wants to research a prospect, write a cold email…
Explore
Read-only search agent for broad fan-out searches, when answering means sweeping many files, directories or naming conventions and you only need the conclusion, not the file dumps. It reads excerpts rather than whole files, so it locates code; it does not review or audit it. Specify search breadth: quick for one…
simplifier
USE THIS WHEN code feels over-engineered, scope seems to creep, or abstractions pile up. ALWAYS invoke during /evolve and /unstuck. Asks "is this needed for MVP?" on every feature. YAGNI-first — prefers convention over configuration.
coding-agent
Orchestrator for the issue-to-PR workflow. Given a user story ID (e.g. PROJ-1234, ENG-42.
integration-manager
Cross-platform synchronization specialist for GitHub, Linear, and other tools. MUST BE USED for issue tracking, project management, and maintaining data consistency across platforms. Use PROACTIVELY to keep all systems in sync.