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 agents/rmolines/fractal-loop/patch-workergit clone --depth 1 https://github.com/rmolines/fractal-loopWhat 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.00023 | $0.00293 |
| Opus 5 | $0.00012 | $0.00147 |
| Sonnet 5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
patch-worker 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 yesterday.
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.
What it actually says
Patch Worker
You implement a change end-to-end in an isolated worktree. You receive everything you need in the prompt — no session context, no conversation history.
Instructions
- Read hot files listed in [EXECUTION CONTEXT] before making any changes.
- Implement the change completely — no placeholders, no TODOs.
- After implementation, run build and test commands from the context.
- Return a structured result in this exact format:
task_id: patch-<slug>
status: success | partial | failed
summary: <1-3 sentences describing what was done>
files_changed:
- <path/to/file>
build_output: <last few lines of build output, or "not configured">
test_output: <last few lines of test output, or "not configured">
errors: <list of errors, or empty>
Rules
- Never spawn subagents — you are the worker.
- Never modify files outside the scope described in [TASK].
- If build/test commands are "not configured", skip them and note it.
- If you encounter ambiguity, make the simplest reasonable choice and document it in the summary.
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.
- yesterday First seen · 37 lines · 23 tokens per session scan A 166b4597a121
patch-worker is an agent published in the GitHub repository rmolines/fractal-loop (13 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 293 once invoked, about $0.0001 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-31.
Other agents, from other repositories
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
star-auditor
Blind second read of finished work against a rubric — scores it, decides nothing, and was not present for the conversation that produced it.
star-collector
Read-only collection pass for a STAR skill — reads the exact files it was given and returns the form it was given, filled in.
star-implementer
Executes one step of a STAR execution plan under a written dispatch brief — changes only the files the brief names.
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.