scheduled-jobs

scheduled-jobs is a skill for Claude Code, Codex from fmind/dot. It costs 19 tokens per session (617 once invoked), scanned A, original, MIT.

A guide for scheduling recurring commands with Linux user timers or macOS LaunchAgents, the operating systems' built-in user-level schedulers.

In plain words
What is it for?
Use it to inspect or create recurring jobs, test one authorized run, review logs, handle missed occurrences, and cancel schedules.
Why use it?
It helps prevent duplicate schedules, unclear environments, missed-run surprises, and jobs that run without a defined limit or stop condition.

Skill for Claude CodeCodex

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

Good fit Use it to inspect or create recurring jobs, test one authorized run, review logs, handle missed occurrences, and cancel schedules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fmind/dot/scheduled-jobs
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 fmind/dot --skill scheduled-jobs
Clone the repo
git clone --depth 1 https://github.com/fmind/dot

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 scheduled-jobs

README.md
[![agentmods](https://agentmods.dev/badge/skills/fmind/dot/scheduled-jobs/github.svg)](https://agentmods.dev/skills/fmind/dot/scheduled-jobs)
Your own site
<a href="https://agentmods.dev/skills/fmind/dot/scheduled-jobs"><img src="https://agentmods.dev/badge/skills/fmind/dot/scheduled-jobs/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 scheduled-jobs

Your own site · 80×15
<a href="https://agentmods.dev/skills/fmind/dot/scheduled-jobs"><img src="https://agentmods.dev/badge/skills/fmind/dot/scheduled-jobs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 617 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00617
Opus 5.5 $0.00008 $0.00247
Sonnet 5.5 $0.00004 $0.00123
Haiku 4.5 $0.00002 $0.00062

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

Security

Grade A, and why

scheduled-jobs 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 9d 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.

skills/scheduled-jobs/SKILL.md · 35 lines

How it starts

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

Scheduled Jobs

Run an existing bounded command through the native user scheduler and prove its outcome. python-script owns program code, and mise owns task commands.

Workflow

  1. Prove one invocation: run the authorized command with explicit arguments and the scheduler's minimal environment. Use an existing dry-run mode when exercising real effects is outside scope; dry-run success does not prove a real run.
  2. Choose the native owner: use Linux user timers or macOS LaunchAgents. Keep an existing project scheduler unless migration is requested. Harness-native agent schedules remain with the matching host skill.
  3. Make execution bounded: use an absolute executable path, explicit working directory, locked dependencies, bounded I/O and runtime, and one writer lock for all entry points. Decide whether a missed occurrence is skipped, coalesced, or replayed; replay requires an idempotent operation.
  4. Prepare the configuration: call the existing command directly, keep branching in tested Python, and validate the unit or plist. Store durable job definitions in their owning repository; do not insert secrets into configuration, command lines, or logs.
  5. Activate within scope: reuse explicit authority for recurring effects and cost. If it is missing, present the validated definition and precise schedule for approval before enabling it; preparing a schedule does not authorize its future effects.
  6. Verify execution: distinguish loaded configuration, next due time, process completion, and the actual application result. Inspect a real scheduler-triggered run; a manual invocation or enabled timer is only partial evidence.
  7. Stop and recover: disable future triggers and separately account for any running process and uncertain external write. Resume only from current state; do not blindly replay a timed-out mutation.

Gotchas

Read the full file on GitHub · 35 lines

Files

What ships with it

2 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.

  1. 9d ago Changed · -3 lines e38ecd414942
  2. 11d ago Changed bfbcbe77ead6
  3. 12d ago Changed · -1 tokens per session 1458edd06b60
  4. 14d ago Changed e97c0476d1b0
  5. 23d ago Changed a0fda2cb8048
  6. 26d ago Changed 2245962429b2
  7. 29d ago Changed · +1 lines · -14 tokens per session 197d26dfe1ff
  8. 1mo ago First seen · 37 lines · 34 tokens per session scan A 661591a47bd5

Subscribe to this mod's changes

scheduled-jobs is a skill published in the GitHub repository fmind/dot (11 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 617 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-09-10.

Related

Other skills, from other repositories

google-workspace-cli

Use gws across Workspace APIs with schema-first calls, profile isolation, bounded reads, and verified Drive, Docs, Sheets, Gmail, Calendar, or Chat writes.

fmind/dotfiles · 38 tokens

handover

Write a self-contained follow-up prompt carrying this session's decisions, constraints, and verified findings into a fresh agent session. Use when handing unfinished work to a new context window.

fmind/dotfiles · 38 tokens

dotfiles-bootstrap

Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.

sebastienrousseau/dotfiles · 88 tokens

vibe

Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…

sebastienrousseau/dotfiles · 137 tokens

telegram

Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…

laurigates/dotfiles · 117 tokens

dotfiles

Chezmoi dotfiles conventions and patterns. Use when modifying dotfiles, adding new managed files, working with chezmoi templates, or syncing agent skills and subagents through agentspec. Do NOT use for installing tools, running doctor, or updating a machine through the dotfiles CLI; use manage-machine.

urmzd/dotfiles · 67 tokens