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 routines-pulsegit 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/routines-pulse)<a href="https://agentmods.dev/skills/djangonavarro220/agentic-life-os/routines-pulse"><img src="https://agentmods.dev/badge/skills/djangonavarro220/agentic-life-os/routines-pulse/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/routines-pulse"><img src="https://agentmods.dev/badge/skills/djangonavarro220/agentic-life-os/routines-pulse.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.00033 | $0.00581 |
| Opus 5 | $0.00016 | $0.00291 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
routines-pulse 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 12d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
routines-pulse
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.
Produce the daily briefing. It is not a giant summary; it is a short decision surface for the day.
Trigger
Use for:
- daily scheduled briefing
- daily briefing requests
- daily pulse requests
- proactive daily synthesis
- morning/evening catch-up when the user wants proactive synthesis
Keep triggers language-neutral in spirit: route by intent, not by examples tied to a specific user's phrasing.
Do not use the daily briefing for tiny status checks. Use routines-heartbeat for silent monitoring and context-now for immediate focus.
Inputs to inspect
Use enabled runtime-owned sources and Life OS pointers, for example:
- current task/TODO state
- upcoming calendar/deadlines if configured
- commitments/follow-ups
- recent heartbeat changes
- user-approved mail/inbox summaries
- project or routine state in
$LIFEOS_DATA_DIR
Never copy raw private content into the public repo. Avoid large transcript dumps. Read enough to decide what matters.
Reasoning steps
- Determine the briefing horizon: today by default.
- Find hard constraints: meetings, deadlines, due commitments, time-sensitive tasks.
- Find soft opportunities: follow-ups, gifts, health/life admin, project momentum.
- Drop stale/noisy items unless they changed or block something.
- Choose 1-3 concrete next actions.
- Mark uncertainty explicitly when source data is thin.
Output contract
Default shape:
Daily briefing:
- Today: ...
- Actions: ...
- Waiting/blockers: ...
- Watch: ...
Rules:
- Keep it compact.
- Prefer actions over trivia.
- Do not include “nothing to report” sections.
- If no actionable changes exist, return a short no-op or silence, depending on runtime policy.
State update
After producing or intentionally skipping a pulse, record safe tracking metadata only when the current runtime policy allows it. Use Life OS private state or runtime-native state as appropriate; do not use helper scripts to decide or perform semantic routine behavior.
What ships with it
1 file 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.
- 12d ago First seen · 87 lines · 33 tokens per session scan A 665b4327107a
routines-pulse is a skill published in the GitHub repository djangonavarro220/agentic-life-os (11 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 581 once invoked, about $0.0002 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.