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/commands/danielmiessler/lifeos/ic)<a href="https://agentmods.dev/commands/danielmiessler/lifeos/ic"><img src="https://agentmods.dev/badge/commands/danielmiessler/lifeos/ic/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/commands/danielmiessler/lifeos/ic"><img src="https://agentmods.dev/badge/commands/danielmiessler/lifeos/ic.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.00117 | $0.00940 |
| Opus 5.5 | $0.00047 | $0.00376 |
| Sonnet 5.5 | $0.00023 | $0.00188 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
ic 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.
What it actually says
/ic — Full-System Integrity Check
Thin invoker. The single source of truth for what this check covers, blocking vs non-blocking rules, and the deep sweep is the IntegrityCheck intent of your release skill (the skill that owns shadow releases and the docs-update intent).
Default (deterministic, under a minute, every check in its own concurrent worker; it writes last-run.json, a runs.jsonl row and Vigil events on every full run, and last-pass.json on a clean one, unless --no-stamp is passed; a --section run writes nothing):
bun ~/.claude/LIFEOS/TOOLS/IntegrityCheck.ts $ARGUMENTS # minus --no-ud, which is this command's flag, not the tool's
Then the documentation update, every run but --section and --no-ud: after the verdict and any fixes, run the DocumentationUpdate intent once with this run's icContext (findings, fix paths, every file /ic changed, contextual findings, change window), so the docs catch up with what /ic fixed. The exact hand-off is the IntegrityCheck intent's Step 3.
Exit codes: 0 clean / 1 blocking / 2 scan error. Exit 2 blocks like exit 1. Orphans block: an unacknowledged orphan workflow is a blocking finding, and so is a guard-count drop until an --accept-drop run on the principal's yes. Report the verdict (CLEAN or N BLOCKING) and, on any blocking finding, the specific broken items with their fix paths.
Flags: --json structured output · --quiet findings only · --section <name> one check, never stamps · --no-stamp writes no stamp file at all · --serial runs the checks one after another (the parity reference) · --since-tag change window from the last v* tag · --run-id <id> recorded in every stamp · --accept-drop rewrites the guard-count snapshot, only on the principal's yes.
The report opens with a Change window — last-run timestamp + areas touched in both repos since. After the tool pass, do a focused contextual review of the top churned areas (judgment: a subsystem rework earns a look, mechanical churn like MEMORY logs does not): do the area's docs/README/ISA still describe what is there now; do the routing surfaces that point into it (CLAUDE.md, PROJECTS.md, the architecture summary, SKILL.md files) still match its shape; did the change orphan or relocate anything the deterministic pass cannot see (renamed dirs still referenced by prose, retired components still listed as live)? Report those findings beside the deterministic verdict; this is a focused read, never an agent sweep. Every full run without --no-stamp is stamped to MEMORY/STATE/integrity/last-run.json + runs.jsonl automatically.
Deep audit (--deep): the deterministic pass PLUS the deep sweep, run as a Claude Code Workflow — the tool never spawns agents itself. Invoke your release skill's IntegrityCheck intent with the argument integrity check --deep and follow it. On an install whose release skill has no such intent, --deep has nothing extra to run: the deterministic pass above is the whole check.
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 · 29 lines · 117 tokens per session scan A d928a16acfb1
ic is a command published in the GitHub repository danielmiessler/LifeOS (19,631 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 940 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 commands, from other repositories
cerrar-sesion
Ritual de cierre de sesión con auditoría, calidad, aprendizajes y contexto para la próxima sesión.
fix-bug
Fix a bug using the knowledge layer — reproduce first, failing regression test, root cause, surgical fix, review and ledger entry after.
check-drift
Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
ar-find
Set AutoFile policy to FIND — restrict edits to existing files only.
audit
Scan Flutter code for anti-patterns across visual, layout, platform, and code-quality categories. Read-only.