Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sonichi/sutandonpx agentmods add skills/sonichi/sutando/morning-briefingWrote 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/sonichi/sutando/morning-briefing)<a href="https://agentmods.dev/skills/sonichi/sutando/morning-briefing"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/morning-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.
<a href="https://agentmods.dev/skills/sonichi/sutando/morning-briefing"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/morning-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.01789 |
| Opus 5.5 | $0.00011 | $0.00716 |
| Sonnet 5.5 | $0.00006 | $0.00358 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
morning-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 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Briefing
Generate a prioritized daily briefing from all your channels.
Usage: /morning-briefing
ARGUMENTS: $ARGUMENTS
What to gather
Step 0 — Calendar cache. CONDITIONAL: Google-calendar hosts only.
src/morning-briefing.py cannot reach the owner's Google Workspace calendar; it reads a cache the
agent writes. Omitting this is silent: the briefing reports "no calendar source is configured.
Connect Google Calendar via Settings → Integrations, or set MORNING_BRIEFING_CALENDAR_SOURCE=macos to
use the local Calendar app". Pull today's local-day events from the
Google connector (order: the Station connector; if not connected, the owner's own
mcp__claude_ai_Google_Calendar__* tools when present; otherwise the one-line note below), then:
echo '[{"raw":"9:00-9:30am 1:1 w/ Sam","calendar":"work"}]' | python3 src/write_calendar_cache.py
python3 src/write_calendar_cache.py --empty # ONLY for a genuinely empty day
Hosts with no Google connector skip STEP 0 ONLY. The reader never touches the local macOS
Calendar or Reminders app on its own (they raise a macOS permission prompt); an owner who wants them
sets MORNING_BRIEFING_CALENDAR_SOURCE=macos once. Step 1 below still runs on every host. See
"Calendar source (Google Workspace) — activation" for the full contract.
A missing connector is one line of text, never a card. If composio_find reports the owner's
calendar or mail app connected: false, say so in the briefing ("Google Calendar isn't connected;
connect it in s.space") and move on. The briefing is not an owner request: never post a connect
card or start a connect-apps wait from it.
Step 1 — Base data (canonical; runs on EVERY host, including hosts that skipped Step 0):
WORKSPACE="$(bash scripts/sutando-config.sh workspace)"
python3 src/morning-briefing.py
src/morning-briefing.py is the single source of truth for core briefing data: weather (Open-Meteo), the calendar cache (or macOS Calendar + Reminders, opt-in only), overnight Discord DMs, pending questions, and system health. It writes output to results/proactive-<ts>.txt and sends a Discord DM directly. Review its output before composing the full briefing — do NOT re-fetch those sources manually.
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.
- today Changed 1e73a2024f2b
- 1mo ago Changed · +3 lines 2442ab8f141c
- 1mo ago Changed · +7 lines d047402fe603
- 2mo ago First seen · 87 lines · 28 tokens per session scan A 3f13b2b39527
morning-briefing is a skill published in the GitHub repository sonichi/sutando (401 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,789 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
notifications
Send notifications through the unified notification router.
outlook
Manage Outlook email — drafting, sending, organizing, rules, vacation replies, and inbox analysis.