What is daily-planning?

A context-aware workflow for planning a day, work session, sprint, or personal agenda from goals, commitments, recent activity, and available context.

Use it to choose what to do next, schedule work blocks, track follow-ups, and prepare wakeups or briefings.

It helps turn scattered obligations and priorities into a realistic order of work instead of a generic task list.

daily-planning — Skill for Claude Code and Codex by CodeInfinity1

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 CodeInfinity1/Stram --skill daily-planning

Clone the repo

git clone --depth 1 https://github.com/CodeInfinity1/Stram

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codeinfinity1/stram/daily-planning/github.svg)](https://agentmods.dev/skills/codeinfinity1/stram/daily-planning)

Your own site

<a href="https://agentmods.dev/skills/codeinfinity1/stram/daily-planning"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/daily-planning/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/skills/codeinfinity1/stram/daily-planning"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/daily-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 787 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.00064	$0.00787
Opus 5.5	$0.00026	$0.00315
Sonnet 5.5	$0.00013	$0.00157
Haiku 4.5	$0.00006	$0.00079

Measured 1mo ago against content hash 400bcd09332b, 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 1mo 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/office-productivity/daily-planning/SKILL.md · 77 lines

How it starts

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

Daily Planning

Purpose

Create a realistic plan for the user from current evidence instead of inventing a generic schedule. This skill adapts patterns from external reference daily planner and founder planner workflows into Stram's cognition, commitment, memory, and wakeup tools.

When To Use

Use when the user asks to plan a day, morning, evening, sprint, work block, or personal assistant agenda. Also use when the user feels scattered and wants the assistant to decide priorities from remembered goals, commitments, activity, and current environment.

Inputs And Evidence

cognitive_state for active goals, tasks, commitments, wakeups, persona, skills, and focus.
memory_summary or memory_search for recent work and stable preferences.
activity_search for recent activity when the user wants context-aware planning.
cognitive_commitment_status for explicit obligations.
system_status or cognitive_environment_status for local environment constraints.

Tool Map

cognitive_state
cognitive_priority_review
cognitive_commitment_status
cognitive_trigger_record
cognitive_briefing_prepare
daily_plan_create
daily_plan_inspect
memory_summary
activity_search
voice_response_prepare

Workflow

Gather current cognitive state and any explicit user constraints such as time window, energy, location, deadline, or "must do" items.
Review commitments and wakeups before adding new tasks; do not duplicate obligations already tracked.
Ask the model to rank tasks using evidence, user preferences, deadlines, risk, dependencies, and environment constraints.
Use daily_plan_create to preserve must-do items, time blocks, waiting/deferred items, risks, evidence refs, and reminder drafts.
Use daily_plan_inspect before responding or before creating any wakeups/commitments.
If responding by voice, prepare a brief spoken summary and leave detailed steps in text or notes.

Safety

Do not infer private calendar details unless provided by tools or user text.
Do not create reminders, messages, purchases, or external actions without explicit approval.
Avoid over-scheduling; preserve focus and recovery time when evidence suggests overload.

Read the full file on GitHub · 77 lines

Files

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.

references/REFERENCE.md 818 B

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.

1mo ago First seen · 77 lines · 64 tokens per session scan A 400bcd09332b

Subscribe to this mod's changes

daily-planning is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 787 once invoked, about $0.0003 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-09-03.

Planning Productivity ai-agent ai-agents ai-tools desktop-automation desktop-automation-software desktop-automation-windows

ask-agents

Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said. Use when the user asks to ask Claude, ask Gemini, ask both, get a second opinion, split reviewer roles, or compare external agents.

chrisblattman/claudeblattman · 55 tokens

review-plan

Review a proposed plan with a single-pass structured critique and a clear verdict. Use when the user asks to review a plan, stress-test a plan, critique a workflow, identify risks, or improve an execution sequence.

chrisblattman/claudeblattman · 46 tokens

alive:settings

The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…

alivecontext/alive · 84 tokens

daily-planning