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 agentmods add skills/sethgammon/citadel/schedulenpx skills add SethGammon/Citadel --skill schedulegit clone --depth 1 https://github.com/SethGammon/CitadelWrote 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/sethgammon/citadel/schedule)<a href="https://agentmods.dev/skills/sethgammon/citadel/schedule"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/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 | $0.00041 | $0.01872 |
| Opus 5 | $0.00020 | $0.00936 |
| Sonnet 5 | $0.00008 | $0.00374 |
| Haiku 4.5 | $0.00004 | $0.00187 |
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 4d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/schedule — Task Scheduling
Orientation
Use when: scheduling a recurring or one-off remote agent run (cron-style, outside the current session). Don't use when: repeating work within the current session (use /loop); continuous unattended campaigns (use /daemon).
Default execution path (READ FIRST)
/schedule add does NOT call CronCreate by default. It shells out to
node scripts/local-schedule.js which installs a native OS entry (Windows
Task Scheduler or Unix cron). Only pass --remote to use Anthropic's routine
system, and only after explicit user confirmation.
Why: CronCreate counts against the account-wide 15 routine runs / 24h
cap; every fire of the scheduled task counts. See
docs/ROUTINE-QUOTA.md.
Default flow — /schedule add "<expr>" "<command>" (no --remote)
Run:
node scripts/local-schedule.js add "<expr>" "<command>"
Then report the returned ID and the removal command. This survives session
end, machine reboot, and consumes zero routine quota. Use
/schedule list and /schedule remove {id} (which also shell out to
local-schedule.js) by default.
Codex automation lane
When running in Codex and the user wants the schedule to survive the current terminal session, create a Codex Automation plan instead of a local OS entry:
node scripts/codex-automation.js plan --type schedule --cadence "<expr>" --command "<command>" --write
Give the returned prompt to the Codex app automation surface and keep the generated .planning/codex-automations/{id}.json as the durable Citadel record.
If .planning/ does not exist, create it before writing automation state.
Opt-in routine flow — /schedule add --remote ...
Only when --remote is explicitly passed:
- Confirm: "This will use
CronCreate, which counts against your 15 routine runs / 24h quota and is cleared at session end. Continue? (y/N)" - On confirmation, run the
CronCreate-based flow documented below.
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.
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.
- 4d ago First seen · 219 lines · 41 tokens per session scan A 44e652612c80
schedule is a skill published in the GitHub repository SethGammon/Citadel (916 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,872 once invoked, about $0.0002 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
compose-org
Run a task as an evolved multi-agent ORG using the installed liquid-org framework — where YOU (the running Claude) embody the org: you ask liquid-org which proven team topology + specialist personas to use (retrieved from its evolved pool, or assembled fresh), then dispatch ONE SUBAGENT PER TALENT to play each role…
liquid-rank
Rank the available skills by RELEVANCE to the current task, on demand, using liquid-org's read-only hermes skill ranker. This is an EXPLICIT, OPT-IN selector you invoke WHEN you want help choosing the most relevant skill for what you're doing — it is NOT default, automatic skill selection, and it does NOT decide for…
present-gate
First-officer gate-presentation rendering — the captain-facing gate-review template and assembly rules, including workflow-owned finding labels. Invoke at the gate point after the FO has decided a stage must be presented.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
ast-grep
Use when asked to run AST-based structural search, lint, or rewrite of code when regex is too fragile. Pattern is validated, blast radius reviewed, and rewrite landed at the correct scope. Don't use for remote, credential, publish, deploy, or irreversible changes.