ruflo-loop-workers
Reviewed
at commit 13af5f1
Caution: Its skills pre-approve Bash and have Claude run the unpinned npm package @claude-flow/cli@latest through npx, so each new version runs without asking.
Cache-aware /loop workers and CronCreate background automation — wraps 5 hooks_worker-* MCP tools (list/dispatch/status/detect/cancel) and exposes 12…
0 upvotes
Log in to upvote or save- Made by
- ruvnet
- Pinned commit
-
13af5f1208960c98832d6d9096a8d7ec45bcdc3e - What we checked
-
Watches calls that start ruflo background workers, refuses ones whose context contains what looks like a secret, and stops dispatching after 100 per session (configurable). It adds a /loop-mod command and writes a small counter file into your project. It reads no prompts or files and makes no network calls.
Review details
Static review of the source at the pinned commit; not run. Delta review of the changes since 87d8687; the rest carries over from the review at that commit. Hooks registered: session.start (registers /loop-mod via $.command.register, reads $.session.root and $.clock.now), tool.call and command.run for loop-mod. tool.call only acts on hooks_worker-* tools: hooks_worker-dispatch is denied when its input matches a secret regex screen (fails closed on oversized input) or when the per-session count reaches maxDispatch (1 to 1000, default 100); other calls pass through. Counters, the last five tool names and settings, never tool input, go to .claude-flow/loop-mod/status.json in the project, failures swallowed. No fetch, process, eval or model calls in the hook. Prompt files: the loop-worker skill pre-approves Bash(npx *) and ScheduleWakeup; the /ruflo-loop command and the loop-worker-coordinator agent tell Claude to run npx @claude-flow/cli@latest hooks worker dispatch/status and then schedule the next run with ScheduleWakeup (270 s or longer). The cron-schedule skill and /ruflo-schedule pre-approve CronCreate, CronList and CronDelete; jobs live in the session and expire after 7 days. The loop-worker skill also tells Claude to follow [LOOP_SUGGESTION] and [CRON_SUGGESTION] hints in MCP tool responses. The ruflo MCP server, the npm package and the workers themselves were not reviewed; scripts/smoke.sh is a local test script not loaded by the plugin. Changes in this version: the only change is a repository field added to plugin.json; no code, prompt or permission changes.
- What it uses
-
- Reads your prompts: no
- Sees tool calls: yes
- Blocks or changes tool calls: yes
- Reads or writes files: yes
- Runs programs on your machine: no
- Calls the model (uses tokens): no
- Sends data over the network: no
- Stores data: yes
- Shows something on screen: yes
Cache-aware /loop workers and CronCreate background automation — wraps 5 hooks_worker-* MCP tools (list/dispatch/status/detect/cancel) and exposes 12 background worker triggers (ultralearn, optimize, consolidate, predict, audit, map, preload, deepdive, document, refactor, benchmark, testgaps). As a mod (ADR-445): a per-session dispatch cap, no secrets in worker context, /loop-mod, and a status file the console shows
Made this mod? Add a badge to your README
Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.
[](https://modsforclaude.com/mods/ruflo-loop-workers/)