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.
npx skills add patleeman/neon-pilot --skill scheduled-tasksgit clone --depth 1 https://github.com/patleeman/neon-pilotWrote 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.
[](https://agentmods.dev/skills/patleeman/neon-pilot/scheduled-tasks)<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.
<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>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.5 | $0.00010 | $0.00821 |
| Sonnet 5.5 | $0.00005 | $0.00410 |
| Haiku 4.5 | $0.00003 | $0.00205 |
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 2mo 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.
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_bashorsubagent
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.
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.
- 2mo ago First seen · 256 lines · 25 tokens per session scan A 25f797292faf
scheduled-tasks is a skill published in the GitHub repository patleeman/neon-pilot (23 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 2,052 once invoked, about $0.0001 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.
scheduled-tasks compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| scheduled-taskspatleeman/neon-pilot | Skill | 23 | 3mo ago | MIT | A | 25 | Claude Code, Codex |
| orbit-notionnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 117 | Claude Code, Codex |
| agentmailpaperclipai/paperclip | Skill | 111k | yesterday | MIT | A | 30 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| rowboat-spacesrowboatlabs/rowboat | Skill | 18k | yesterday | Apache-2.0 | A | 60 | Claude Code, Codex |
| feishuHmbown/CodeWhale | Skill | 41k | 5d ago | MIT | A | 33 | Claude Code, Codex |
| pinchtab-mcppinchtab/pinchtab | Skill | 11k | 10d ago | MIT | A | 52 | Claude Code, Codex |