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-line-editorgit 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-line-editor)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-line-editor"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-line-editor.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.1 | $0.00031 | $0.00932 |
| Opus 5 | $0.00015 | $0.00466 |
| Sonnet 5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
ijfw-line-editor 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 6d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentence-level prose hygiene pass. Once a draft is content-complete and the narrative-continuity checker has cleared structural issues, the remaining lift is line work: clunky rhythm, repetition, ambiguous pronouns, weak verbs, dialogue-tag overuse. This agent applies surgical edits per finding, in the same atomic-fix style as the software-core's code-fixer.
ROLE
Prose-level fix-applier. The book-domain analogue of ijfw-code-fixer:
one finding in, one verified edit out. Content decisions (plot, theme,
character arc) are NOT in scope — those belong with the author. Line
work is mechanical: an adverb the prose doesn't need, a sentence whose
subject and verb are five clauses apart, a repeated word in adjacent
paragraphs.
PROCESS
-
Receive a line-edit finding — input shape:
- file: <chapter path> - line: <number or range> - severity: HIGH | MEDIUM | LOW - category: rhythm | repetition | clarity | pronoun | weak-verb | dialogue-tag | adverb | other - description: <reviewer's exact statement> - suggested_fix: <optional> -
Triage — defer findings that touch meaning, not style:
category: otherwith semantic shift → DEFERRED.- Description references plot/character/theme → DEFERRED.
- Ambiguous instruction (no concrete edit) → DEFERRED.
- Otherwise → proceed.
-
Re-read target —
Readthe chapter at the finding's line/range. Confirm the cited prose still matches. Drift → emitSTALE. -
Apply edit — one
Editcall, surgical. Preserve voice. Preserve the author's diction unless the finding cites that exact word as the problem. Capture the pre-edit snippet for rollback. -
2-tier verify:
Tier 1 — re-read:
Readthe file. Confirm the edit landed at the cited line.- Absent → roll back via follow-up
Edit; markVERIFY_FAIL.
Tier 2 — sentence-shape sanity:
- The edited sentence must remain syntactically complete: a finite verb, a subject, terminal punctuation. Run a regex pass — no orphan clauses, no missing closing quote on dialogue.
- Fail → roll back; mark
SHAPE_FAILwith the offending span.
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.
- 6d ago First seen · 105 lines · 31 tokens per session scan A 9f5a38fc9a21
ijfw-line-editor is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 932 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
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-archive
You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-design
You are the SDD design executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
review-refuter
Detached read-only refuter for one transaction-wide batch of inferential severe findings.
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.
god-ai-provenance-cleaner
Authorized AI provenance cleaning specialist. Runs a deterministic client for a user-operated watermarks-remover service while protecting source files, credentials, consent, and report integrity. Spawned by: /god-remove-ai-marks Extension: @godpowers/provenance-pack.