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.
curl -O https://raw.githubusercontent.com/c0dezli/claude-code-personal-assistant/main/.claude/agents/daily-schedule-agent.mdgit clone --depth 1 https://github.com/c0dezli/claude-code-personal-assistantWrote 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/agents/c0dezli/claude-code-personal-assistant/daily-schedule-agent)<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="Measured on agentmods" height="20"></a>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 | $0.00006 | $0.00481 |
| Sonnet 5 | $0.00003 | $0.00193 |
| Haiku 4.5 | $0.00001 | $0.00096 |
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 8d 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.
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.mdfor 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.mdexactly - 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)
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.
- 8d ago First seen · 98 lines · 13 tokens per session scan A 4bb212178c75
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. 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 agents, from other repositories
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.