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 opensourcemanagementgit 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/opensourcemanagement)<a href="https://agentmods.dev/skills/danielmiessler/lifeos/opensourcemanagement"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/opensourcemanagement/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/opensourcemanagement"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/opensourcemanagement.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.00212 | $0.02492 |
| Opus 5.5 | $0.00085 | $0.00997 |
| Sonnet 5.5 | $0.00042 | $0.00498 |
| Haiku 4.5 | $0.00021 | $0.00249 |
Grade A, and why
OpenSourceManagement 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 today.
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSourceManagement
Contents: Ideal State · Intent Routing · Repos · Quick Reference · Data & Config · Gotchas · Examples
Triages and manages GitHub activity across the principal's open source repos, the OSS_REPOS list in Config.md. Repos outside that list are out of scope; when Config.md routes one elsewhere (for example a repo another skill triages), point there. Through the gh CLI it checks and prioritizes issues, recommends which PRs to merge or review, reads discussions, gives a cross-repo state snapshot, and posts a single bot comment that edits in place via hidden HTML markers instead of stacking new comments each time.
Ideal State
- Every report comes from this session's live
ghfetch, structured per repo, with items ranked by urgency and impact, each repo's community mood rated (positive, neutral, negative), and specific next actions with suggested responses, written direct and actionable. - A fetch that failed or hit its limit is named as a hole or a truncation, never rendered as a quiet repo.
- No public "fixed", "merged" or "done" claim goes out before the change lands in the source of truth (Gotchas: FIX-IN-SOURCE-FIRST), and a recurring bot note is one marker comment edited in place, never a stack.
- A private repo goes public only as an audited, fresh-history export that reads READY, with a problem-first README, a license and a social preview image, and only on the principal's word naming that repo.
- Local-model checks name what is new in the Ollama library, whether each fits and is already on the local model box, and leave every pull to the principal.
Intent Routing
| Intent | Trigger | File |
|---|---|---|
| CheckIssues | "check issues", "open source issues", " issues" | Intents/CheckIssues.md |
| CheckPullRequests | "check PRs", "pull requests", "review PRs", "open PRs" | Intents/CheckPullRequests.md |
| CheckDiscussions | "check discussions", "community discussions", "what are people asking" | Intents/CheckDiscussions.md |
| CheckState | "open source state", "project state", "check our open source", "what needs attention" | Intents/CheckState.md |
| PostMarkerComment | "post triage comment", "leave a marker comment", "edit-in-place comment", "update bot comment", "upsert comment" | Intents/PostMarkerComment.md |
| LocalModels | "new open source models", "latest open-weight models", "what should I pull", "do we have ", "new Ollama models" | Intents/LocalModels.md |
| GoPublic | "is X public-ready", "take this repo public", "open source this", "prep X for public release" | Intents/GoPublic.md |
What ships with it
16 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.
- Intents/CheckDiscussions.md 4.7 KB
- Intents/CheckIssues.md 4.1 KB
- Intents/CheckPullRequests.md 4.9 KB
- Intents/CheckState.md 6.1 KB
- Intents/GoPublic.md 9.8 KB
- Intents/LocalModels.md 2.2 KB
- Intents/PostMarkerComment.md 5.6 KB
- Setup.md 4.5 KB
- Tools/Fetch.help.md 2.3 KB
- Tools/Fetch.ts 11 KB runs code
- Tools/LocalModels.help.md 3.1 KB
- Tools/LocalModels.ts 9.7 KB runs code
- Tools/LocalModelsLib.ts 4.8 KB runs code
- Tools/MarkerComment.ts 11 KB runs code
- Tools/PublicReady.help.md 4.0 KB
- Tools/PublicReady.ts 27 KB runs code
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.
- today First seen · 129 lines · 212 tokens per session scan A f8402395faad
OpenSourceManagement is a skill published in the GitHub repository danielmiessler/LifeOS (19,616 stars, last pushed today), licensed MIT. It adds 212 tokens to every session and 2,492 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
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
fleet-audit
Publish the findings of an autonomous fleet audit as one continuously-rewritten issue per audit stream on the GitOps repository's forge, and propose fixes as narrow remediation pull requests (merge requests on GitLab).
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
shipyard-executing-plans
Executes a written implementation plan with agents. Use when a written plan is ready to execute, in the current session or a separate one. Also use when the user says "build this", "implement this", "execute the plan", or "run the plan", or when a loaded plan file has independent tasks suitable for agent dispatch.