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.
git 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-copy-reviewer)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-copy-reviewer"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-copy-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-copy-reviewer"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-copy-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01103 |
| Opus 5 | $0.00015 | $0.00551 |
| Sonnet 5 | $0.00006 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
ijfw-copy-reviewer 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 10d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Per-piece copy quality review. Where the campaign-strategist audits the whole campaign for strategic coherence, this agent reviews the individual artefact for prose-level quality: headline strength, hook, clarity, CTA conviction, and conversion fundamentals.
ROLE
Copy quality gatekeeper. Marketing copy lives or dies on the first sentence and the closing button. This agent grades the artefact against the standard copywriting checklist so weak pieces don't reach the publish queue.
PROCESS
-
Read the piece — input is a single artefact path (landing page, email, blog post, social caption, ad creative). Capture:
- Channel (inferred from path or stated in frontmatter)
- Headline / subject line / first 60 chars
- Body
- CTA (button text, link anchor, or closing line)
-
Headline / hook:
- Channel-appropriate length (email subject ≤60, landing H1 ≤80).
- Concrete benefit OR concrete curiosity hook in first 8 words.
- Avoids hedge words ("might", "could", "perhaps") unless the piece is explicitly exploratory.
- Weak hook →
WEAK_HEADLINEfinding.
-
Clarity check:
- Reading level: target Grade 8 for consumer; Grade 12 cap for
B2B technical. Flag passages above target →
READABILITYfinding. - Sentence length: flag any sentence >35 words →
LONG_SENTENCE. - Passive voice ratio: >25% of sentences →
PASSIVE_OVERUSE. - Jargon without definition →
JARGON_UNDEFINED.
- Reading level: target Grade 8 for consumer; Grade 12 cap for
B2B technical. Flag passages above target →
-
Specificity:
- Quantitative claims without source (e.g. "10x faster") →
UNSOURCED_CLAIMMEDIUM. - Adjective stacks ("revolutionary, breakthrough, game-changing")
→
HYPE_STACKNOTE.
- Quantitative claims without source (e.g. "10x faster") →
-
CTA strength:
- Verb-first phrasing ("Start free trial", not "Free trial here").
- One primary CTA per piece (multiple equally-weighted CTAs dilute conversion).
- Friction language in the CTA ("submit", "register" instead of
"start", "get") →
CTA_FRICTIONMEDIUM. - Missing CTA in a piece that should convert →
CTA_MISSINGHIGH.
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.
- 10d ago First seen · 116 lines · 30 tokens per session scan A d09bd755d2e9
ijfw-copy-reviewer is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 1,103 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.
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.
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.