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/eric-cielo/moflo/spell-schedulenpx skills add eric-cielo/moflo --skill spell-schedulegit clone --depth 1 https://github.com/eric-cielo/mofloWrote 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/eric-cielo/moflo/spell-schedule)<a href="https://agentmods.dev/skills/eric-cielo/moflo/spell-schedule"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/spell-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.00099 | $0.02058 |
| Opus 5 | $0.00049 | $0.01029 |
| Sonnet 5 | $0.00020 | $0.00412 |
| Haiku 4.5 | $0.00010 | $0.00206 |
Grade A, and why
spell-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 5d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spell-schedule — Schedule a Local Spell
This skill walks the user through scheduling a moflo spell on the local moflo daemon.
Schedules live in moflo's memory store and are evaluated once per minute by the daemon's poll loop.
Execution goes through the same engine path as flo spell cast.
Not the same as
/schedule./schedulecreates remote Anthropic-cloud routines; this skill drives the local daemon scheduler.
Arguments: $ARGUMENTS (optional spell name/alias to pre-select)
When to use
The user says any of:
- "schedule the X spell"
- "run X every "
- "fire X once at "
- "set up a recurring run for X"
- "I want X to run every morning"
If the user wants a cloud agent (mentions "remote", "GitHub Actions", "Anthropic cloud", or specifies a repo to clone), redirect them to /schedule.
Workflow
Step 1 — Verify the daemon is running
npx flo doctor 2>&1 | grep -i daemon
If the daemon is not running, prompt the user:
- "The moflo daemon isn't running. Schedules only fire while the daemon is up. Start it now?"
- If yes:
npx flo daemon start. - If they decline, warn the user that the schedule will be created but won't fire until the daemon is started.
OS-native autostart (launchd / systemd / Task Scheduler) is automatic: the
first flo spell schedule create registers the daemon as a login service so
schedules survive reboot, and the cancel that takes the enabled-schedule count
to 0 unregisters it. Users only need to think about it in two cases:
--no-autostartoncreate— skip registration (use in containers/CI where the daemon is already managed externally).--keep-autostartoncancel— keep the login service registered through a cancel-then-recreate dance.
Step 2 — Identify the target spell
If $ARGUMENTS was provided, use it as the spell name/alias. Otherwise, list spells and let the user pick:
npx flo spell list 2>&1
The output is a markdown table with columns: name, alias, description, source. Both name and alias are valid for flo spell schedule create -n <value> — prefer the full name to avoid alias conflicts.
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.
- 5d ago First seen · 180 lines · 99 tokens per session scan A 0a9ac42fc415
spell-schedule is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 2,058 once invoked, about $0.0005 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
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
cao-session-management
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.
material-organizer
Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.