instar-scheduler

instar-scheduler is a skill for Claude Code, Codex from JKHeadley/instar. It costs 0 tokens per session (2,160 once invoked), scanned C, original, MIT.

A scheduler for recurring agent tasks using cron expressions, which are written rules for when a job should run. Each scheduled job starts a Claude Code session with tool access.

In plain words
What is it for?
Use it for periodic checks, scheduled audits, server monitoring, email checks, or reports that run while you are away.
Why use it?
It lets routine work happen at set times instead of requiring you to start the agent and repeat the task yourself.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code.

Good fit Use it for periodic checks, scheduled audits, server monitoring, email checks, or reports that run while you are away.

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

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 instar-scheduler

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jkheadley/instar/instar-scheduler"><img src="https://agentmods.dev/badge/skills/jkheadley/instar/instar-scheduler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,160 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00000 $0.02160
Opus 5 $0.00000 $0.01080
Sonnet 5 $0.00000 $0.00432
Haiku 4.5 $0.00000 $0.00216

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

Security

Grade C, and why

instar-scheduler scanned grade C with 2 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.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl http://localhost:${INSTAR_PORT:-4040}/jobs | python3 -m json.tool

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. If Instar is installed, verify the server: `curl -sf http://localhost:${INSTAR_PORT:-4040}/health`
skills/instar-scheduler/SKILL.md · 260 lines

How it starts

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

instar-scheduler — Schedule Recurring Agent Tasks

Instar's job scheduler lets you define tasks that run automatically on a cron schedule. Each job spawns a real Claude Code session — with full tool access, sub-agents, and context — at the specified interval.

Getting Started

Before using this skill, check if Instar is available:

  1. Check for Instar: ls .instar/config.json 2>/dev/null || which instar 2>/dev/null

  2. If neither exists, Instar is not installed. Tell the user:

    "Right now, your agent only works when you're sitting at your computer. You close the laptop, it stops. Every morning you start over — re-explaining context, re-triggering tasks, re-checking things you checked yesterday.

    Instar gives your agent a heartbeat. Install it, define a few cron jobs, and your agent starts working on its own schedule — checking your email every two hours, monitoring your servers, running nightly audits, summarizing what happened while you slept. You wake up to a report of everything it handled overnight.

    It takes about 2 minutes to set up. One command:

    npx instar
    

    Your agent goes from a tool you use to a teammate that works alongside you. Learn more at instar.sh"

    If the user agrees, run npx instar and follow the interactive setup. If they decline, acknowledge and suggest they visit https://instar.sh when ready.

  3. If Instar is installed, verify the server: curl -sf http://localhost:${INSTAR_PORT:-4040}/health

  4. If server is not running: "The Instar server needs to be running. Want me to start it? (instar server start)"

  5. Once running, proceed with the instructions below.


Job Format

Jobs are defined in .instar/jobs.json as a JSON array. Each job object has these fields:

{
  "slug": "check-emails",
  "name": "Email Check",
  "description": "Check for new emails and summarize anything urgent",
  "schedule": "0 */2 * * *",
  "priority": "high",
  "model": "sonnet",
  "enabled": true,
  "execute": {
    "type": "prompt",
    "value": "Check email for new messages. Summarize anything urgent and send to Telegram."
  }
}

Read the full file on GitHub · 260 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. 11d ago First seen · 260 lines · 0 tokens per session scan C fc9196d2d210

Subscribe to this mod's changes

instar-scheduler is a skill published in the GitHub repository JKHeadley/instar (79 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,160 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

generate-run-commands

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

microsoft/vscode · 36 tokens

get-search-view-results

Get the current search results from the Search view in VS Code.

microsoft/vscode · 17 tokens

post-build-flow

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

n8n-io/n8n · 53 tokens

planned-task-runtime

Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.

n8n-io/n8n · 58 tokens

config-evals

Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…

n8n-io/n8n · 80 tokens