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 jatinmayekar/openwiki-for-claude-code --skill schedulegit clone --depth 1 https://github.com/jatinmayekar/openwiki-for-claude-codeWrote 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/jatinmayekar/openwiki-for-claude-code/schedule)<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="Measured on agentmods" 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.00055 | $0.00779 |
| Opus 5 | $0.00028 | $0.00390 |
| Sonnet 5 | $0.00011 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
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 8d 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 — 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
/scheduleskill to create a routine that runs/openwiki:updateon the repo, then commits and pushes the changedopenwiki/. 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/--allowedToolsso it can edit files and run git without prompting.
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.
- 8d ago First seen · 46 lines · 55 tokens per session scan A 44e411e6d98f
schedule is a skill published in the GitHub repository jatinmayekar/openwiki-for-claude-code (18 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 779 once invoked, about $0.0003 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.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.