Throwaway probe for the factory loop: can an agent a mod spawns from a timer call that mod's own tool?
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin timer-spawn-probe in cbundy/dev-system. Commands read from the repo's manifest — 14 days ago.
pingerProbe agent that calls the timer-spawn-probe ping tool.
The old name of fabriek, the same plugin, kept as a second marketplace name for the 10-minor-release window so a workspace whose settings still enable callum-flow@callum keeps its guard hooks. Install only one of the two.
7 skills · hooks
Skills (update-dev, onboard, evaluate-sessions, query-factory-data, factory-state, backlog-triage, dependency-chain) and hooks for working in a dev-system repo.
7 skills · hooks
The issue orchestrator as a deterministic loop: claims, gates and merges a repo's ready issues in code and wakes Claude only for judgment calls. For orchestrator workspaces (the orchestrator-loop Coder template); not enabled by default.
2 skills · 6 agents
The workspace probe's spawner: spawns one agent from a timer, as the factory loop does
1 agent
Opt-in mod: a status entry with the time, context fill, plan usage, factory counts and tool versions on every surface, including mobile and desktop through Remote Control.
The factory loop's companion, enabled beside factory-loop: starts each agent the loop runs in its worktree slot, confines its writes and pushes, gives its commands a 10-minute timeout, and holds a writer's finish while the repo's gates fail.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.