A guide for scheduling automatic updates to an OpenWiki repository. OpenWiki is a project wiki that documents a code repository.

Use it when you want daily or recurring wiki updates through a cloud routine, a desktop task, or an active session.

It explains how to keep documentation refreshed on a schedule and how the available scheduling methods differ in durability and machine requirements.

schedule — Skill for Claude Code by jatinmayekar

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 jatinmayekar/openwiki-for-claude-code --skill schedule

Clone the repo

git clone --depth 1 https://github.com/jatinmayekar/openwiki-for-claude-code

Made for: Claude Code.

Or install openwiki, the plugin that ships this one along with the rest of its 4 skills.

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/jatinmayekar/openwiki-for-claude-code/schedule/github.svg)](https://agentmods.dev/skills/jatinmayekar/openwiki-for-claude-code/schedule)

Your own site

<a href="https://agentmods.dev/skills/jatinmayekar/openwiki-for-claude-code/schedule"><img src="https://agentmods.dev/badge/skills/jatinmayekar/openwiki-for-claude-code/schedule/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/jatinmayekar/openwiki-for-claude-code/schedule"><img src="https://agentmods.dev/badge/skills/jatinmayekar/openwiki-for-claude-code/schedule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 779 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.00055	$0.00779
Opus 5.5	$0.00022	$0.00312
Sonnet 5.5	$0.00011	$0.00156
Haiku 4.5	$0.00006	$0.00078

Measured 2mo ago against content hash 44e411e6d98f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/openwiki/skills/schedule/SKILL.md · 46 lines

How it starts

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

OpenWiki: schedule automatic updates

Help the user keep the wiki fresh automatically by running /openwiki:update on a schedule. Every option here is keyless — Claude Code does the work under the plan the user already pays for.

Critical safety rule: for any scheduled claude -p invocation, never use --bare. Bare mode skips OAuth and demands ANTHROPIC_API_KEY, which silently bills API rates instead of using the subscription. Always use a normal (non-bare) claude -p "/openwiki:update".

Step 1 — pick a mechanism

Use AskUserQuestion to let the user choose, explaining the tradeoffs:

Option	Durable?	Needs machine on	Notes
Cloud Routine (`/schedule`)	Yes	No	Runs on Anthropic infra under the user's plan. Min interval 1h. Fresh clone → the routine must commit & push the updated `openwiki/`. Best "daily at a set time, unattended."
Desktop scheduled task	Yes	Yes	Runs locally on the user's machine via `claude -p "/openwiki:update"` (non-bare) in the repo. Good when it needs local files.
In-session `/loop` / CronCreate	No — expires in 7 days	Yes + open session	Quick and fully keyless in the current session, but session-scoped and auto-expires after 7 days. Good for a trial, not set-and-forget.
OpenWiki GitHub Action	Yes (CI)	No	Only for users already running the OpenWiki CLI in CI. Not keyless — CI needs a provider API secret. Mention only if they ask.

Also ask for the time (default: daily 09:00 local). Note cron uses local timezone and adds jitter, so times like 3 9 * * * fire more predictably than 0 9 * * *.

Step 2 — set up the chosen option

In-session (CronCreate): create a recurring task with a daily cron expression (e.g. 3 9 * * *) whose prompt is /openwiki:update. Confirm the job id, and clearly warn the user it runs only while this session is open and idle, and expires after 7 days (recreate to extend).
Cloud Routine: guide the user to run the /schedule skill to create a routine that runs /openwiki:update on the repo, then commits and pushes the changed openwiki/. Explain it runs unattended on their plan.
Desktop scheduled task: guide the user to create a daily OS/desktop task running claude -p "/openwiki:update" (non-bare) from the repo directory, with appropriate --permission-mode/--allowedTools so it can edit files and run git without prompting.

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

2mo ago First seen · 46 lines · 55 tokens per session scan A 44e411e6d98f

Subscribe to this mod's changes

schedule is a skill published in the GitHub repository jatinmayekar/openwiki-for-claude-code (19 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 779 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.

CI and CD DevOps and cloud

schedule next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
schedulejatinmayekar/openwiki-for-claude-code	Skill	19	4mo ago	MIT	A	55	Claude Code
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	11d ago	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.1k	yesterday	MIT	A	56	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	yesterday	MIT	C	54	Claude Code
managing-github-actions-secretsPostHog/posthog-foss	Skill	728	yesterday	MIT	A	67	Claude Code, Codex
postman-newman-automationLambdaTest/agent-skills	Skill	390	yesterday	MIT	A	156	Claude Code, Codex