daily-task-manager

daily-task-manager is a skill for Claude Code, Codex from timurgaleev/memex. It costs 31 tokens per session (486 once invoked), scanned A, original, MIT.

A task-list manager that stores tasks in a structured page and tracks them from creation through completion or postponement. It supports four priority levels, from urgent work to backlog items.

In plain words
What is it for?
Use it to add, complete, defer, remove, or review daily tasks, including due dates, priorities, completion dates, and reasons for postponement.
Why use it?
It gives tasks a consistent home and records what was completed or why something was deferred. This makes the active list easier to review by priority.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/timurgaleev/memex/daily-task-manager
Any agent
npx skills add timurgaleev/memex --skill daily-task-manager
Clone the repo
git clone --depth 1 https://github.com/timurgaleev/memex

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-task-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/timurgaleev/memex/daily-task-manager.svg)](https://agentmods.dev/skills/timurgaleev/memex/daily-task-manager)
Your own site
<a href="https://agentmods.dev/skills/timurgaleev/memex/daily-task-manager"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/daily-task-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 486 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00031 $0.00486
Opus 5 $0.00015 $0.00243
Sonnet 5 $0.00006 $0.00097
Haiku 4.5 $0.00003 $0.00049

Measured 5d ago against content hash 9e4d92f93e3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

daily-task-manager 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 5d 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.

deploy/skills/daily-task-manager/SKILL.md · 74 lines

What it actually says

Daily Task Manager

Contract

This skill guarantees:

  • Tasks stored as a brain page (tasks/tasks.md) with structured format
  • Task lifecycle: add → in-progress → complete | defer
  • Priority levels: P0 (urgent), P1 (today), P2 (this week), P3 (backlog)
  • Completed tasks archived with completion date
  • Deferred tasks carry forward with reason

Phases

  1. Load current tasks. page_get tasks/tasks — read the task list.
  2. Execute the requested action:
    • Add: Append task with priority, description, due date. Record it with add_timeline_event.
    • Complete: Mark as done, move to completed section with date.
    • Defer: Move to next day/week with reason.
    • Remove: Delete from list (rare, prefer complete or defer).
    • Review: Display all active tasks by priority.
  3. Save. page_put tasks/tasks — write updated task list.

Output Format

# Tasks

## P0 — Urgent
- [ ] {task description} (due: {date})

## P1 — Today
- [ ] {task description}

## P2 — This Week
- [ ] {task description}

## P3 — Backlog
- [ ] {task description}

## Completed
- [x] {task} (completed: {date})

Anti-Patterns

  • Adding tasks without a priority level
  • Completing tasks without recording the completion date
  • Deferring tasks without a reason
  • Letting the task list grow unbounded (review weekly)
  • Storing tasks outside the brain (they should be searchable)
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. 5d ago First seen · 74 lines · 31 tokens per session scan A 9e4d92f93e3d

Subscribe to this mod's changes

daily-task-manager is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 486 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/obsidian-mcp-server · 62 tokens

api-context

Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.

cyanheads/obsidian-mcp-server · 79 tokens

api-canvas

DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…

cyanheads/obsidian-mcp-server · 85 tokens

api-testing

Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.

cyanheads/obsidian-mcp-server · 46 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/obsidian-mcp-server · 76 tokens

maintenance

Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…

cyanheads/obsidian-mcp-server · 75 tokens