scheduling-tasks

scheduling-tasks is a skill for Claude Code, Codex from letta-ai/letta-code. It costs 40 tokens per session (2,436 once invoked), scanned A, original, Apache-2.0.

A scheduling tool for creating and managing reminders and recurring tasks through the letta cron command-line tool. A scheduled task sends a prompt to the agent at a chosen time or interval.

In plain words
What is it for?
Creating one-time reminders, recurring check-ins and delayed follow-ups, as well as listing, inspecting, replacing or cancelling scheduled tasks.
Why use it?
It removes the need to remember delayed or repeated work manually and lets users inspect, replace or cancel schedules.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Creating one-time reminders, recurring check-ins and delayed follow-ups, as well as listing, inspecting, replacing or cancelling scheduled tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/letta-ai/letta-code/scheduling-tasks
About the project

letta-ai/letta-code is an agent harness for building assistants that retain memory, identity, and experience across interactions instead of treating each task as isolated. Developers use it through local, desktop, browser, or messaging interfaces for interactive or continuously running agents, and its catalogue entries configure the agents' skills, instructions, rules, and behavior.

letta-ai/letta-code · 3,675 stars · on GitHub · letta.com

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 letta-ai/letta-code --skill scheduling-tasks
Clone the repo
git clone --depth 1 https://github.com/letta-ai/letta-code

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 scheduling-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/letta-ai/letta-code/scheduling-tasks/github.svg)](https://agentmods.dev/skills/letta-ai/letta-code/scheduling-tasks)
Your own site
<a href="https://agentmods.dev/skills/letta-ai/letta-code/scheduling-tasks"><img src="https://agentmods.dev/badge/skills/letta-ai/letta-code/scheduling-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.

agentmods 80×15 button for scheduling-tasks

Your own site · 80×15
<a href="https://agentmods.dev/skills/letta-ai/letta-code/scheduling-tasks"><img src="https://agentmods.dev/badge/skills/letta-ai/letta-code/scheduling-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,436 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00040 $0.02436
Opus 5.5 $0.00016 $0.00974
Sonnet 5.5 $0.00008 $0.00487
Haiku 4.5 $0.00004 $0.00244

Measured 26d ago against content hash 6dafd56471b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scheduling-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 26d 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.

src/skills/builtin/scheduling-tasks/SKILL.md · 228 lines

How it starts

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

Scheduling Tasks

This skill lets you create, list, and manage scheduled tasks using the letta cron CLI. Scheduled tasks send a prompt to the agent on a timer — useful for reminders, periodic check-ins, and deferred follow-ups.

For ordinary one-shot or recurring work in the current conversation, use Wake instead. Wake is self-bound and covers create, list, and cancel without routing choices.

When to Use This Skill

  • The task should run in a fresh, default, or different conversation
  • The task needs a specific connected computer
  • You need run history, replacement, or broader schedule inspection
  • Wake cannot see or manage the schedule you need

Where Schedules Run

Execution determines schedule ownership; there is no runner selection flag:

  • In a managed Cloud sandbox, schedules are durable Cloud schedules and run in the agent's Cloud sandbox.
  • On a user-managed computer or self-hosted runtime, schedules are local and fire only while a Letta session is running there.

From a managed Cloud sandbox, --computer <deviceId> can run the scheduled work on a specific connected computer. Get the device ID from letta computers list. If that computer is offline at fire time, execution falls back to the Cloud sandbox. Local execution cannot target another computer.

Creation and execution follow those rules, while management commands still show and cancel both local and Cloud inventory. This keeps schedules created by older CLI versions visible without changing where new schedules run.

CLI Usage

All commands go through letta cron via the Bash tool. Output is JSON.

Creating a Task

letta cron add --name <short-name> --description <text> --prompt <text> <schedule>

Required flags:

Flag Description
--name <text> Short identifier for the task (e.g. "dog-walk-reminder")
--description <text> Human-readable description of what the task does
--prompt <text> The message that will be sent to the agent when the task fires

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

  1. 26d ago Changed · -9 lines · -2 tokens per session 6dafd56471b5
  2. 27d ago Changed · +4 lines · -7 tokens per session ea7f0214c54e
  3. 1mo ago Changed 18bccc0be0ef
  4. 1mo ago First seen · 233 lines · 49 tokens per session scan A 910b6b5e1994

Subscribe to this mod's changes

scheduling-tasks is a skill published in the GitHub repository letta-ai/letta-code (3,675 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 2,436 once invoked, about $0.0002 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.