daily-rundown

daily-rundown is a skill for Claude Code, Codex from agno-agi/context. It costs 87 tokens per session (1,615 once invoked), scanned A, original, Apache-2.0.

A read-only morning briefing that combines important updates, meetings, reminders, emails, and Slack conversations into one short daily summary when those sources are connected.

In plain words
What is it for?
Use it to see what needs your attention each morning, including unanswered updates, upcoming or overdue work, relevant email, and Slack threads.
Why use it?
It removes the need to check several apps separately and filters out information that does not need attention today.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is _**Runtime skill** — a playbook the deployed @context agent runs for its owner, invoked in natural language. Not a coding-agent workflow; those live in [`.agent.

Good fit Use it to see what needs your attention each morning, including unanswered updates, upcoming or overdue work, relevant email, and Slack threads.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/agno-agi/context
agentmods
npx agentmods add skills/agno-agi/context/daily-rundown

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-rundown

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/agno-agi/context/daily-rundown"><img src="https://agentmods.dev/badge/skills/agno-agi/context/daily-rundown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,615 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.00087 $0.01615
Opus 5 $0.00044 $0.00807
Sonnet 5 $0.00017 $0.00323
Haiku 4.5 $0.00009 $0.00161

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

Security

Grade A, and why

daily-rundown 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.

skills/daily-rundown/SKILL.md · 110 lines

How it starts

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

Daily Rundown

Runtime skill — a playbook the deployed @context agent runs for its owner, invoked in natural language. Not a coding-agent workflow; those live in .agents/skills/.

A focused today brief: one glanceable surface instead of five apps. It folds in the inbound queue, the CRM, the real calendar, the inbox, and Slack — each source only when it's connected — and stitches them into one short digest. Read-only assembly: it pulls and formats, it never files or sends anything.

The whole value is one surface, so stay ruthless about signal. Surface what needs the owner's eyes today, not a mirror of every inbox and channel.

Procedure

Keep it cheap, and fire it once. Each source is a sub-agent call under its own time budget, and they all share one model — so keep the fan-out small and issue it in a single concurrent batch: put the backbone and best-effort tool calls in one message, all at once, so the brief's wall-clock is the slowest source, not the sum. One tight retrieval per source, no exploratory follow-ups, never retry a source. Don't run the sources in separate turns one after another — that serializes their budgets and is the slow path.

The backbone (the two fast local sources below) always runs and carries the brief on its own; the best-effort sources get skipped the moment they're slow, error, or come back empty (see the skip rule). A complete-but-fast brief beats a perfect one that hangs.

  1. Anchor on now, in the owner's zone. Read the current datetime from your context — it carries the owner's timezone, with the zone label shown (e.g. PDT). "Today" is now → end of that local day, and every due/overdue/"today" judgment is made in that zone, not UTC. Render each time with its zone label so nothing is ambiguous. If the owner asks for a different zone ("rundown in GMT"), frame and render the whole brief in that zone instead. Don't auto-detect travel: the configured zone (or the one they ask for) is the source of truth.

Read the full file on GitHub · 110 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. 10d ago First seen · 110 lines · 87 tokens per session scan A 45d254975607

Subscribe to this mod's changes

daily-rundown is a skill published in the GitHub repository agno-agi/context (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,615 once invoked, about $0.0004 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.