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 djangonavarro220/agentic-life-os --skill integrations-runtimegit clone --depth 1 https://github.com/djangonavarro220/agentic-life-osWrote 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/djangonavarro220/agentic-life-os/integrations-runtime)<a href="https://agentmods.dev/skills/djangonavarro220/agentic-life-os/integrations-runtime"><img src="https://agentmods.dev/badge/skills/djangonavarro220/agentic-life-os/integrations-runtime/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/djangonavarro220/agentic-life-os/integrations-runtime"><img src="https://agentmods.dev/badge/skills/djangonavarro220/agentic-life-os/integrations-runtime.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.00025 | $0.01961 |
| Opus 5 | $0.00013 | $0.00981 |
| Sonnet 5 | $0.00005 | $0.00392 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
integrations-runtime 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 10d ago.
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
integrations-runtime
Mandatory integrity contract
Before acting, load and follow ../../references/data-integrity.md. Its provenance, missing-value, correction-history, defensive-write, backup, and recovery rules are mandatory for this subskill.
Bridge Life OS playbooks to runtime-owned capabilities without duplicating secrets or private data. Life OS is a helper/coordination layer: each skill records its own source decisions, pointers, access instructions, operational state, caches, and Life-OS-specific preferences; real user data usually stays in Hermes/OpenClaw or an external source.
Trigger
Use when a Life OS workflow needs to inspect, use, bridge, import from, or configure a runtime-owned capability:
- skills and skill visibility
- tasks or background task ledgers
- cron jobs, schedules, reminders, hooks, heartbeats, standing orders
- delivery routes and messaging platforms
- tools, sandboxing, models, providers
- memory systems, vaults, credentials
- agents, profiles, workspaces, channel bindings
- mail/calendar or other external integrations
Principle
Discovery and integration choices are semantic agent work. Do not encode them in helper scripts.
The LLM should inspect the active runtime with runtime-native commands and docs, explain what it found, choose or propose the source of truth, then record that decision in the owning skill data file. Helper scripts may validate files or create local state containers, but they must not decide which runtime system to use or migrate.
Runtime adapters
Load the adapter matching the active runtime before making runtime-specific recommendations or changes:
runtimes/hermes.mdruntimes/openclaw.md
The adapters are central and apply to all Life OS skills. Individual subskills may add narrow runtime notes only when they differ from the central adapter.
Runtime discovery loop
- Identify the active runtime and scope:
- Hermes profile
- OpenClaw agent/workspace
- other runtime, if neither adapter matches
- Load the runtime adapter.
- Run read-only native discovery commands.
- Classify each capability:
- not present
- present and runtime-owned
- present but disabled
- present but ambiguous
- missing facts require user/runtime docs
- Decide the Life OS relationship:
- ignore for this workflow
- read when relevant
- record a source pointer and bridge through runtime tools
- store Life-OS-specific preference/technical state in config
- create a runtime-native store when no suitable source exists, then record the pointer
- migrate/reconnect references when moving runtimes, with approval before changes
- Ask approval before any side effect.
- Store domain source decisions, access notes, operational state, caches, and Life-OS-specific preferences in the owning skill data file under
$LIFEOS_DATA_DIR/<skill-name>/data.json. Do not store full real-domain data just to make Life OS the owner.
What ships with it
3 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.
- 10d ago First seen · 200 lines · 25 tokens per session scan A 794e98c82d50
integrations-runtime is a skill published in the GitHub repository djangonavarro220/agentic-life-os (11 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 1,961 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…