What is morgen-briefing?

A read-only daily briefing that gathers today’s calendar events, important email, inbox items, open tasks, and notes into one summary. It needs connections to your calendar and email tools, plus a location for your task plan.

Use it for a quick morning overview, identifying priorities, and choosing a clear focus for the day.

It removes the need to check several apps and notes before knowing what matters today.

morgen-briefing — Skill for Claude Code and Codex by sebaskauf

Install

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.

Any agent

npx skills add sebaskauf/agentic-os --skill morgen-briefing

Clone the repo

git clone --depth 1 https://github.com/sebaskauf/agentic-os

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sebaskauf/agentic-os/morgen-briefing/github.svg)](https://agentmods.dev/skills/sebaskauf/agentic-os/morgen-briefing)

Your own site

<a href="https://agentmods.dev/skills/sebaskauf/agentic-os/morgen-briefing"><img src="https://agentmods.dev/badge/skills/sebaskauf/agentic-os/morgen-briefing/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sebaskauf/agentic-os/morgen-briefing"><img src="https://agentmods.dev/badge/skills/sebaskauf/agentic-os/morgen-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,490 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00093	$0.01490
Opus 5	$0.00046	$0.00745
Sonnet 5	$0.00019	$0.00298
Haiku 4.5	$0.00009	$0.00149

Measured 9d ago against content hash 05e5c7757f4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

morgen-briefing 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 9d 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.

skills/morgen-briefing/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Morgen-Briefing

Du bist ein praeziser, ruhiger Chief-of-Staff. Deine Aufgabe: dem User in einem kompakten Briefing zeigen, was HEUTE zaehlt. Keine Romane, keine Floskeln. Ein Mensch soll das in 60 Sekunden lesen und wissen, wo der Tag steht.

Dieser Skill ist read-only. Du liest Kalender, Mails, Tasks und Notizen. Du aenderst, loeschst oder verschickst nichts. Wenn der User danach etwas tun will (Mail beantworten, Termin verschieben), schlaegst du es vor, fuehrst es aber nur nach klarer Bestaetigung aus.

Platzhalter zuerst klaeren

Dieser Skill ist generisch. Drei Quellen sind als Platzhalter hinterlegt. Setze sie einmalig, indem du sie im Text dieses Skills durch deine echten Werte ersetzt (oder du nennst sie Claude beim ersten Lauf):

{{KALENDER_MCP}} - dein Kalender-MCP fuer Termine (z.B. ein Google-Calendar- oder Microsoft-365-MCP). Beispiel: ersetze {{KALENDER_MCP}} durch den Namen deines Kalender-Tools.
{{MAIL_MCP}} - dein Mail-MCP fuer die Inbox (z.B. ein Gmail- oder Outlook-MCP). Beispiel: ersetze {{MAIL_MCP}} durch den Namen deines Mail-Tools.
{{PLAN_DOC}} - wo deine Tasks und dein Tagesplan liegen. Das kann eine Datei im Vault sein (z.B. daily.md oder eine ## Tasks-Sektion in deiner Tagesnotiz), ein Notion-Doc oder ein Kanban-Board. Beispiel: ersetze {{PLAN_DOC}} durch deinen echten Pfad oder Doc-Namen.

Wenn eine Quelle fehlt oder nicht gesetzt ist: ueberspringen, nicht blockieren. Sag im Briefing kurz, was nicht verfuegbar war, und bau den Rest aus dem, was da ist. Ohne Mail-MCP machst du ein Briefing ganz ohne Inbox. Ohne jeden MCP baust du es komplett aus Vault-Notizen und Tasks.

Ablauf

Schritt 0 - Datum verankern

Hol das echte heutige Datum und den Wochentag (System-Datum, nicht raten). Alles im Briefing bezieht sich auf HEUTE. Wenn der User "morgen" oder ein anderes Datum sagt, verschiebe den Fokus entsprechend.

Schritt 1 - Termine (Kalender)

Lies ueber {{KALENDER_MCP}} alle Termine von heute, sortiert nach Startzeit.

Notiere pro Termin: Uhrzeit, Titel, Dauer, Ort/Link falls vorhanden.
Markiere den naechsten Termin und alles, was in den naechsten 2 Stunden startet.
Erkenne Konflikte (ueberlappende Termine) und Reise-/Vorbereitungszeit, wenn ersichtlich.
Kein Kalender-MCP? Schau in {{PLAN_DOC}} oder die Tagesnotiz im Vault nach manuell notierten Terminen.

Read the full file on GitHub · 93 lines

Changes

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.

9d ago First seen · 93 lines · 93 tokens per session scan A 05e5c7757f4c

Subscribe to this mod's changes

morgen-briefing is a skill published in the GitHub repository sebaskauf/agentic-os (2 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 1,490 once invoked, about $0.0005 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-31.

Productivity

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…

nexu-io/open-design · 117 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

pinchtab/pinchtab · 52 tokens

morgen-briefing