Schedule workers to run checks at fixed times while a Claude Code session stays open. Set up recurring security scans, test coverage analysis, or documentation tasks, and find or cancel scheduled jobs.
Schedule persistent background workers via CronCreate
Review the instructions the agent will receive before you install.
Use CronCreate for a worker that should fire on a clock while this Claude Code session is open:
CronCreate({ cron: "*/15 * * * *", prompt: "Dispatch the audit worker with mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch({ trigger: \"audit\" }) and report anything critical", recurring: true })
The parameters are cron (five-field expression), prompt and recurring. A schedule: field does not exist. These jobs live in the session: they stop when you close it, and recurring jobs expire on their own after 7 days. Cancel one sooner with CronDelete (find its id with CronList). For a worker that must keep running after the session ends, use /schedule (cloud routines) or an OS scheduler (cron, systemd timer) that calls npx @claude-flow/cli@latest hooks worker dispatch --trigger audit.
| Worker | Cron | Description |
|---|---|---|
| audit | */15 * * * * | Security scanning |
| optimize | */30 * * * * | Performance optimization |
| consolidate | 0 * * * * | Memory consolidation |
| map | */30 * * * * | Codebase mapping |
| testgaps | */15 * * * * | Test coverage analysis |
| document | 0 */2 * * * | API documentation |
/loop: In-session, self-pacing. Use for active development./schedule or an OS scheduler: Survives the session. Use for CI-style monitoring.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.