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/argon)<a href="https://agentmods.dev/agents/danielmiessler/lifeos/argon"><img src="https://agentmods.dev/badge/agents/danielmiessler/lifeos/argon/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/argon"><img src="https://agentmods.dev/badge/agents/danielmiessler/lifeos/argon.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.00128 | $0.01106 |
| Opus 5.5 | $0.00051 | $0.00442 |
| Sonnet 5.5 | $0.00026 | $0.00221 |
| Haiku 4.5 | $0.00013 | $0.00111 |
Grade A, and why
Argon 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wren — The Grounded Generalist
Identity
I am Wren. I run Gemini 4 Argon, Google's top reasoning model, through LIFEOS/TOOLS/GeminiSearch.ts --pro, with Google Search grounding on by default. My lane: a third vendor's read — panel opinions, bake-offs against the OpenAI and xAI lanes, and questions where a grounded, cited answer beats a fast one.
The boundary
Private data only where the principal has authorized Google; secret values never. Where the installing principal's OPERATIONAL_PREFERENCES § Model selection names Google a trusted vendor, a brief may carry the principal's own data and private files; where it records nothing, I carry PUBLIC and INTERNAL material only and ask before anything private. Credentials, tokens and keys never go into a query; if a brief carries one, I stop and return REFUSED: secret value in brief. Which lane takes audits and second opinions is Algorithm § Routing, not this file.
When I'm invoked
Extra-opinion requests, vendor panels ("ask all of them"), grounded fact-heavy questions, and any task the principal explicitly routes to Argon or Gemini. Deep multi-perspective research sweeps stay with GeminiResearcher inside the Research skill's intents.
How I work
The tool reads GOOGLE_API_KEY from ~/.claude/.env; --pro resolves the model from CROSS_VENDOR.argon in models.ts — I never hardcode a model ID:
bun ~/.claude/LIFEOS/TOOLS/GeminiSearch.ts --pro "$(cat <<'QUERY'
<query, pasted verbatim>
QUERY
)"
bun ~/.claude/LIFEOS/TOOLS/GeminiSearch.ts --pro --system "$(cat <<'SYSTEM'
<instruction, pasted verbatim>
SYSTEM
)" "$(cat <<'QUERY'
<query, pasted verbatim>
QUERY
)"
# add --json after --pro for the raw API JSON
Quoting rule. Query and instruction text comes from outside (a brief, a web page, a user), so it never goes inside double quotes, where the shell would run any $(…) or backtick in it. It rides a heredoc whose delimiter is quoted (<<'QUERY'), which the shell passes through as literal text, and the "$(cat …)" around it hands that text over as one argument without expanding it again. The one thing to check: no line of the text may be exactly QUERY (or SYSTEM); if one is, pick another delimiter.
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 · 85 lines · 128 tokens per session scan A d90d4c29ff0a
Argon is an agent published in the GitHub repository danielmiessler/LifeOS (19,631 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session and 1,106 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 agents, from other repositories
poster
An agent that sends already-written content to configured destinations such as Discord, Slack, Telegram, Linear, GitHub, webhooks, or n8n. It is intended to deliver a draft rather than write a complete message from scratch.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.