ijfw-research-lead

ijfw-research-lead is an agent for Claude Code from FerroxLabs/ijfw. It costs 34 tokens per session (1,446 once invoked), scanned A, original, MIT.

A research-project reviewer that checks whether the questions, methods, sources, and conclusions fit together.

In plain words
What is it for?
Use it before combining research findings or reviewing a research project, especially for literature reviews, source lists, and synthesis drafts.
Why use it?
It finds unsupported conclusions, missing source types, mismatched methods, and research that has drifted beyond its agreed scope.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the ijfw plugin — 34 skills, 22 commands, 37 agents, 6 hooks shipped together

Good fit Use it before combining research findings or reviewing a research project, especially for literature reviews, source lists, and synthesis drafts.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ferroxlabs/ijfw/ijfw-research-lead
Install

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.

Clone the repo
git clone --depth 1 https://github.com/FerroxLabs/ijfw

Made for: Claude Code.

Or install ijfw, the plugin that ships this one along with the rest of its 34 skills, 22 commands, 37 agents, 6 hooks.

Wrote 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.

agentmods badge for ijfw-research-lead

README.md
[![agentmods](https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-research-lead/github.svg)](https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-research-lead)
Your own site
<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-research-lead"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-research-lead/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.

agentmods 80×15 button for ijfw-research-lead

Your own site · 80×15
<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-research-lead"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-research-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,446 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01446
Opus 5 $0.00017 $0.00723
Sonnet 5 $0.00007 $0.00289
Haiku 4.5 $0.00003 $0.00145

Measured 9d ago against content hash 3d06e36877fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ijfw-research-lead 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 9d 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.

claude/agents/ijfw-research-lead.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Audit research artefacts — research questions, methodology notes, literature reviews, source ledgers, synthesis drafts — against the declared question + methodology. Reports structural-fit gaps that single-section review can't catch. The research-domain analogue of the software-core's plan-checker.

ROLE

Research-project integrity gatekeeper. A researcher can write a tight literature review whose individual citations are sound, then quietly draw a synthesis claim that none of those citations actually support. Or commit to a quantitative methodology in the question phase and ship a synthesis based on three anecdotes. This agent reads the whole project and grades:

  • Question alignment — does every section serve the declared research_question?
  • Methodology fit — does the actual evidence base match the declared methodology?
  • Source coverage — are the source types declared in the brief represented in the ledger? Are obvious source gaps flagged?
  • Synthesis integrity — does each synthesis claim cite a source in the ledger, and does that source actually support the claim?
  • Scope discipline — do findings stay within scope_constraints or has the project drifted out of scope?

PROCESS

  1. Locate the brief — default research/BRIEF.md or whatever path the invocation supplies. Parse:

    • research_question, methodology, sources, output_format, scope_constraints.
  2. Enumerate artefactsGlob research/**/*.md and any subdirectories (research/sources/, research/notes/, research/synthesis/). Read each.

  3. Per-section audit:

    • Question alignment: does each section's stated or implied scope map to the brief's research_question? Off-target → QUESTION_DRIFT.
    • Methodology fit: count evidence type per claim. If the brief declares quantitative but ≥30% of cited evidence is anecdotal → METHODOLOGY_MISMATCH HIGH. If the brief declares literature review but synthesis includes original data collection without justification → SCOPE_CREEP.
    • Source ledger: every cited source must appear in a consolidated source list (research/sources.md or per-source notes). Missing entries → LEDGER_GAP.
    • Coverage: cross-reference declared sources array against the ledger. Declared source type with zero entries → SOURCE_TYPE_MISSING MEDIUM.

Read the full file on GitHub · 146 lines

Changes

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.

  1. 9d ago First seen · 146 lines · 34 tokens per session scan A 3d06e36877fd

Subscribe to this mod's changes

ijfw-research-lead is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,446 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.