What is scheduled-tasks?

Instructions for creating and managing scheduled automations that run prompts or background jobs at a specified time or on a repeating schedule.

Use them to create one-time reminders, recurring checks, scheduled prompts, or periodic conversation wake-ups.

They provide commands for listing, validating, running, and troubleshooting automations that need to operate without an open conversation.

scheduled-tasks — Skill for Claude Code and Codex by patleeman

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 patleeman/neon-pilot --skill scheduled-tasks

Clone the repo

git clone --depth 1 https://github.com/patleeman/neon-pilot

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/patleeman/neon-pilot/scheduled-tasks/github.svg)](https://agentmods.dev/skills/patleeman/neon-pilot/scheduled-tasks)

Your own site

<a href="https://agentmods.dev/skills/patleeman/neon-pilot/scheduled-tasks"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/scheduled-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/patleeman/neon-pilot/scheduled-tasks"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/scheduled-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,052 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.00025	$0.02052
Opus 5	$0.00013	$0.01026
Sonnet 5	$0.00005	$0.00410
Haiku 4.5	$0.00003	$0.00205

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

Security

Grade A, and why

scheduled-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 10d 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.

extensions/system-automations/skills/scheduled-tasks/SKILL.md · 256 lines

How it starts

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

Scheduled Tasks

Scheduled tasks are the durable automation system behind saved scheduled prompts.

Use them when something should happen:

later
on a recurring schedule
as either a background job or a conversation-thread wakeup
without an active conversation open

CLI

For Neon Pilot administration from shell, prefer the CLI:

neon-pilot tasks list --json
neon-pilot tasks get <task-id> --json
neon-pilot tasks save --title "Daily check" --cron "0 9 * * *" --prompt "Summarize status" --json
neon-pilot tasks validate --title "One shot" --at "2026-06-10T09:00:00Z" --prompt "Follow up" --json
neon-pilot tasks run <task-id> --json
neon-pilot tasks delete <task-id> --json
neon-pilot heartbeats start <heartbeat-id> --interval-minutes 5 --conversation-id <conversation-id> --prompt "Wake up, check whether work remains, and stop this heartbeat when done." --json
neon-pilot heartbeats list --json
neon-pilot heartbeats stop <heartbeat-id> --json

Use the unified neon_pilot internal tool from inside a model turn when direct tool execution is more appropriate than shell administration. scheduled_task remains available for low-level scheduled task management, but recurring self-admin heartbeats should go through the Neon Pilot admin surface.

When to use scheduled tasks

Good fits:

morning reports
recurring reviews
unattended background prompts
durable conversation jobs that should resume a thread later
automation that should surface attention on its owning thread
task-style work that may optionally callback into a conversation later

Do not confuse scheduled tasks with:

project tasks in state.yaml — those are planning/checklist items
follow-up queue entries — those are conversation-bound wakeups
durable background runs — those are detached jobs launched on demand with background_bash or subagent

Where automations live

Canonical storage:

~/.local/state/neon-pilot/daemon/runtime.db

Automation definitions and scheduler runtime state now live in the daemon SQLite database.

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

10d ago First seen · 256 lines · 25 tokens per session scan A 25f797292faf

Subscribe to this mod's changes

scheduled-tasks is a skill published in the GitHub repository patleeman/neon-pilot (23 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 2,052 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.

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

scheduled-tasks