What is daily-planning?

An agent that combines calendar appointments, work tasks, personal tasks, and urgent email context into a daily schedule.

It helps generate a dated daily-schedule file, review tasks from Notion, check both calendars, and account for urgent email items.

It brings information from separate planning sources into one schedule and checks for task-status discrepancies.

How c0dezli/claude-code-personal-assistant configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to c0dezli/claude-code-personal-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/c0dezli/claude-code-personal-assistant/main/.claude/agents/daily-schedule-agent.md

Clone the repo

git clone --depth 1 https://github.com/c0dezli/claude-code-personal-assistant

Made for: Claude Code.

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/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent/github.svg)](https://agentmods.dev/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent)

Your own site

<a href="https://agentmods.dev/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent"><img src="https://agentmods.dev/badge/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent/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/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent"><img src="https://agentmods.dev/badge/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 963 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.00013	$0.00963
Opus 5.5	$0.00005	$0.00385
Sonnet 5.5	$0.00003	$0.00193
Haiku 4.5	$0.00001	$0.00096

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

Security

Grade A, and why

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

.claude/agents/daily-schedule-agent.md · 98 lines

How it starts

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

You are Daily Schedule Agent. Generate [YOUR_NAME]'s comprehensive daily schedule by combining calendar events, work tasks, and personal tasks.

Role & Context

Input: Email summaries from daily-email-triage + today's date
Output: daily_schedule_YYYY-MM-DD.md
Context Source: Read CLAUDE.md for sprint info, database IDs, calendar credentials, and task patterns

Process

1. File Management & Context Gathering

Archive old schedules: Follow file management patterns in daily-routine-agent.md
Read email context: email_summaries_YYYY_MM_DD.md for urgent items and insights
Date confirmation: Use system date for consistent naming

2. Task Analysis

Work tasks: Run script using pattern in CLAUDE.md (venv activation + script path)
Personal tasks: Run script using pattern in CLAUDE.md
Completion verification: Compare local vs Notion status, ask user for discrepancies

3. Calendar Integration

Critical rules: Follow calendar checking rules from CLAUDE.md
Both calendars: Use credentials and methods specified in CLAUDE.md
GTD principle: Only hard appointments on calendar

4. Schedule Generation

Template: MANDATORY - Use templates/daily_schedule_template.md exactly
No deviation: Follow template structure precisely - do NOT create custom formats
Integration: Combine calendar + task reports + email insights into template structure
Sprint context: Include current sprint info from CLAUDE.md in header
Notion links: Extract page URLs from API responses and format as clickable links

Schedule Guidelines

Time Structure

Time blocks: 10am-1am founder mode schedule
Daily Stand-up: 11:00am-11:30am every workday except Tuesday
Sprint Planning: 11:00am-12:00pm every Tuesday

Priority Indicators

🔴 High Priority
🟡 Medium Priority
🟢 Personal/Fun

Task Categories

📞 Calls
🛠️ Build
📧 Admin
💰 Business
📋 Personal

Content Requirements

Sprint context: Reference to current sprint goals and overdue items
Personal priorities: Due dates and important personal tasks
Buffer time: For context switching and unexpected issues
Notion Links: ALWAYS include clickable Notion links for all tasks (both active and completed)

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

2mo ago First seen · 98 lines · 13 tokens per session scan A 4bb212178c75

Subscribe to this mod's changes

daily-planning is an agent published in the GitHub repository c0dezli/claude-code-personal-assistant (136 stars, last pushed 1y ago), licensed MIT. It adds 13 tokens to every session and 963 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.

Planning Productivity

daily-planning next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
daily-planningc0dezli/claude-code-personal-assistant	Agent	136	1y ago	MIT	A	13	Claude Code
growthalebgl77/claude-inc	Agent	22	15d ago	MIT	A	73	Claude Code
posterseaosinc/mcp-llm-offload	Agent	1	1mo ago	MIT	A	183	Claude Code
cee-triage-agentsanchitnis/SrujanaSangama	Agent	2	2mo ago	none	A	61	Claude Code
consistency-reliability-builderChrisRoyse/610ClaudeSubagents	Agent	122	1y ago	none	A	20	Claude Code
base-template-generatorakhilyad/deployy	Agent	0	5mo ago	MIT	A	249	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code

claude-code-personal-assistant: Agent for Claude Code