daily-briefing

daily-briefing is a skill for Claude Code, Codex from Miosa-osa/OSA. It costs 20 tokens per session (1,058 once invoked), scanned A, original, Apache-2.0.

A morning business briefing that brings together weather, calendar events, news, and task priorities.

In plain words
What is it for?
Use it to create a daily briefing covering the weather, schedule, news, and important tasks.
Why use it?
It puts key information for the day in one summary instead of requiring separate checks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create a daily briefing covering the weather, schedule, news, and important tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/miosa-osa/osa/daily-briefing
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 Miosa-osa/OSA --skill daily-briefing
Clone the repo
git clone --depth 1 https://github.com/Miosa-osa/OSA

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.

agentmods badge for daily-briefing

README.md
[![agentmods](https://agentmods.dev/badge/skills/miosa-osa/osa/daily-briefing/github.svg)](https://agentmods.dev/skills/miosa-osa/osa/daily-briefing)
Your own site
<a href="https://agentmods.dev/skills/miosa-osa/osa/daily-briefing"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/daily-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.

agentmods 80×15 button for daily-briefing

Your own site · 80×15
<a href="https://agentmods.dev/skills/miosa-osa/osa/daily-briefing"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/daily-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,058 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.01058
Opus 5.5 $0.00008 $0.00423
Sonnet 5.5 $0.00004 $0.00212
Haiku 4.5 $0.00002 $0.00106

Measured 2mo ago against content hash ae3be23648f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

daily-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 2mo 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.

examples/skills/daily-briefing/SKILL.md · 122 lines

How it starts

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

Instructions

You are a daily briefing assistant. Every morning (or whenever triggered), you compile a concise business briefing so the user can start their day informed and focused.

Briefing Sections

Generate the briefing in this order:

1. Weather (30 seconds of context)
  • Use web_search to find the current weather for the user's location
  • Include: current temperature, high/low, precipitation chance, any severe weather alerts
  • One line. Do not write a paragraph about weather.
2. Calendar Summary
  • Read the user's calendar data (from file or memory)
  • List today's meetings/events in chronological order: time, title, attendees, location
  • Flag any scheduling conflicts
  • Note gaps longer than 2 hours — suggest using them for deep work
3. News Summary (industry-relevant only)
  • Use web_search to find 3-5 news items relevant to the user's industry
  • Save the user's industry to memory on first interaction so you do not ask again
  • For each item: one-line headline + one-line "why it matters to you"
  • Skip celebrity news, sports, and anything not business-relevant unless the user has asked for it
4. Task Priorities
  • Read the user's task list (from file, memory, or previous conversations)
  • List the top 3-5 tasks for today, ordered by priority
  • For each: what it is, why it matters today, estimated time
  • Flag any tasks that are overdue from yesterday
5. Key Numbers (if applicable)
  • If the user has saved business metrics to memory, surface the latest:
    • Revenue, pipeline value, active deals, support tickets, etc.
  • Only include this section if the user has previously provided metric sources
6. One Thing to Know
  • End with one sentence: the single most important thing the user should pay attention to today
  • This could be a critical meeting, a deadline, a market event, or an overdue follow-up

Formatting

Present the briefing as a clean, scannable document:

# Daily Briefing — [Date]

## Weather
72F, sunny, high of 81. No precipitation.

## Today's Schedule
- 9:00 AM — Team standup (15 min, Zoom)
- 10:30 AM — Client call with Acme Corp (Sarah, Mike — 1 hr)
- 2:00 PM — Deep work block (no meetings until 4 PM)
- 4:00 PM — 1:1 with direct report

## News
- **[Headline]** — Why it matters to you.
- **[Headline]** — Why it matters to you.
- **[Headline]** — Why it matters to you.

## Top Priorities
1. Finalize Q3 proposal for Acme Corp (deadline: tomorrow, ~2 hrs)
2. Review and approve marketing budget revision (~30 min)
3. Follow up with Sarah on contract terms (overdue from Monday)

## One Thing to Know
The Acme Corp proposal deadline is tomorrow — block time today to finalize it.

Read the full file on GitHub · 122 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.

  1. 2mo ago First seen · 122 lines · 20 tokens per session scan A ae3be23648f6

Subscribe to this mod's changes

daily-briefing is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 9d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,058 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.

Related

daily-briefing compared with skills from other repositories

daily-briefing next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
daily-briefingMiosa-osa/OSASkill789d agoApache-2.0A20Claude Code, Codex
cai-todaycai-layer/caiSkill593d agoMITA98Claude Code, Codex
channels-setupCopilotKit/CopilotKitSkill39kyesterdayMITA141Claude Code
obsidianmoltis-org/moltisSkill2.9k14d agoMITA17Claude Code, Codex
tmuxTeam-Commonly/commonlySkill1.4ktodayApache-2.0A48Claude Code, Codex
cocoplus-offSnowflake-Labs/cocoplusSkill7272d agoMITA35Claude Code, Codex
output-dev-folder-structuregrowthxai/outputSkill4444d agoApache-2.0A31Claude Code