What is schedule-tasks?

A tool for creating, viewing, deleting, and reviewing scheduled Claude Desktop tasks. These tasks run Claude Code automatically on a cron schedule, meaning a time pattern such as daily or weekly.

Use it to automate recurring project work, manage existing schedules, or analyze previous runs and refine their prompts.

It keeps recurring work running after the current session ends. Reviewing past logs can help improve a task's instructions.

schedule-tasks — Skill for Claude Code by d-gangz

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 d-gangz/dgang-skills --skill schedule-tasks

Clone the repo

git clone --depth 1 https://github.com/d-gangz/dgang-skills

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/skills/d-gangz/dgang-skills/schedule-tasks/github.svg)](https://agentmods.dev/skills/d-gangz/dgang-skills/schedule-tasks)

Your own site

<a href="https://agentmods.dev/skills/d-gangz/dgang-skills/schedule-tasks"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/schedule-tasks/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/d-gangz/dgang-skills/schedule-tasks"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/schedule-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,725 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.00128	$0.01725
Opus 5	$0.00064	$0.00863
Sonnet 5	$0.00026	$0.00345
Haiku 4.5	$0.00013	$0.00172

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

Security

Grade A, and why

schedule-tasks 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 11d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/create-scheduled-task.sh, scripts/delete-scheduled-task.sh, scripts/list-scheduled-tasks.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/schedule-tasks/SKILL.md · 158 lines

How it starts

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

Claude Code Scheduled Tasks

Manage scheduled tasks that run Claude Code headlessly inside Claude Desktop on a cron schedule. Four operations: create, list, delete, and analyze logs to improve prompts.

All operations default to the current project directory ($PWD) as the target folder.

Key Paths

SKILL.md prompts: ~/.claude/scheduled-tasks/{task-name}/SKILL.md
Schedule config: ~/Library/Application Support/Claude/claude-code-sessions/{project-id}/{agent-session-id}/scheduled-tasks.json
Session metadata: Same directory as config, in local_{run-id}.json files
Session transcripts: ~/.claude/projects/{project-hash}/{cli-session-id}.jsonl (shared with regular CLI sessions)

Operations

1. Create a Scheduled Task

Gather these from the user (use AskUserQuestion if anything is unclear):

Task name (kebab-case, e.g. daily-review)
Description (short, shown in Desktop UI)
Prompt (the full instructions for what the task should do)
Cron expression (in local timezone — remind the user of this)
Model (default: claude-opus-4-6)

The project folder defaults to $PWD. Don't ask unless the user wants a different folder.

Run the bundled create script:

bash <skill-path>/scripts/create-scheduled-task.sh \
  "<name>" "<description>" "<prompt>" "<cron>" "<model>" "<folder>"

If the prompt is long or complex, write it to a temp file first and pass @/path/to/file as the prompt argument — the script handles this.

After creation, remind the user:

Restart Claude Desktop to load the new task.
Click "Run Now" on the task in Claude Desktop, then immediately stop the run. The task must be triggered manually at least once before the cron schedule will take effect — without this initial run, subsequent scheduled runs will not execute.

Common cron expressions (local timezone):

0 8 * * * — daily at 8 AM
0 8 * * 1-5 — weekdays at 8 AM
30 23 * * * — daily at 11:30 PM
0 9 * * 1 — every Monday at 9 AM
*/5 * * * * — every 5 minutes (warn about API costs)

Read the full file on GitHub · 158 lines

Files

What ships with it

3 files 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.

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.

11d ago First seen · 158 lines · 128 tokens per session scan A d72670a23324

Subscribe to this mod's changes

schedule-tasks is a skill published in the GitHub repository d-gangz/dgang-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 128 tokens to every session and 1,725 once invoked, about $0.0006 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.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

schedule-tasks