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/ferroxlabs/ijfw/ijfw-ralph-loop-runnergit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/agents/ferroxlabs/ijfw/ijfw-ralph-loop-runner)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-ralph-loop-runner"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-ralph-loop-runner.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 | $0.00031 | $0.01014 |
| Opus 5 | $0.00015 | $0.00507 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
ijfw-ralph-loop-runner 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 4d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watch the wave-state checkpoint stream for orphaned subagents (last checkpoint present but no DONE status) and re-dispatch them with prior-checkpoint context so they pick up exactly where they truncated. Closes the v1.4.4 W10-A2 / A3 / B2 truncation-recovery gap that cost orchestrator context.
ROLE
Truncation recovery loop. In v1.4.4, 3 of 6 Wave 10 subagents truncated at 19-28 tool uses; the orchestrator detected silence and re-read worktree state manually. This agent makes that recovery deterministic and offloads it from the orchestrator's context window.
PROCESS
-
Locate active wave -- read
.ijfw/wave-<id>/STATE.mdfor the current phase. Accept explicitwaveIdinput or auto-detect the most recently modified.ijfw/wave-*/directory. -
Enumerate subagents -- list
.ijfw/wave-<id>/subagent-*.checkpoint.jsonfiles. For each, read shape{tool_use_count, last_action, files_*, next_step, blockers?, timestamp}. -
Detect orphans -- invoke
listOrphanedSubagents(waveId, projectRoot)frommcp-server/src/orchestrator/subagent-telemetry.js(provided by S1 prelude). An orphan = checkpoint exists, no DONE in last 90s, no new checkpoint in last 60s. -
For each orphan, write a resume-brief to
.planning/<phase>/resume-<subId>.md:- Original task summary (read from blackboard claim).
- Last checkpoint snapshot (verbatim JSON).
- "Next step" pointer the subagent stated.
- Explicit instruction: continue from
next_step; do NOT redo completedfiles_created/files_modifiedwork.
-
Update RALPH-LOG.md -- append H3 entry per orphan with disposition:
RESUMED <subId>: brief written + suggested dispatch command logged.STALE <subId>: no useful checkpoint; recommend fresh redispatch.RESOLVED <subId>: DONE status posted since last poll; no action.
-
Exit signal: emit gate-result.
- Any RESUMED -> severity NOTE (recovery happened; informational).
- All RESOLVED + no orphans -> PASS.
- Any STALE -> MEDIUM (caller should consider scope-narrowing for re-dispatch).
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.
- 4d ago First seen · 94 lines · 31 tokens per session scan A 696c19478ba3
ijfw-ralph-loop-runner is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 11d ago), licensed MIT. It adds 31 tokens to every session and 1,014 once invoked, about $0.0002 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 agents, from other repositories
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
nopua-mentor-ja
Agent Team メンター役 — 他のチームメイトの実行状況を観察し、恐怖ではなく知恵で導く。行き詰まり、放棄、受け身に陥ったときは道徳経の知恵で啓発。5人以上のチーム推奨。.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
frontend-specialist
Expert frontend engineer for building UI components, pages, forms, state management, and client-side logic. Adapts to any frontend framework based on project context.
god-show-hn-strategist
Show HN launch strategist. Knows HN audience, title conventions, comment norms. Refuses launch-day pump-and-dump and pre-fab marketing-speak. Spawned by: /god-show-hn Extension: @godpowers/launch-pack.