ijfw-plan-checker

ijfw-plan-checker is an agent for Claude Code from FerroxLabs/ijfw. It costs 26 tokens per session (1,103 once invoked), scanned A, original, MIT.

A planning review tool that compares a proposed implementation plan with the files and code already in a project. It flags planned new files or changes that may already exist.

In plain words
What is it for?
Use it before dispatching implementation work. It reads a phase plan, checks referenced paths and code symbols, and reports possible overlaps for review.
Why use it?
It helps avoid rebuilding infrastructure that has already been written. This reduces duplicate work and catches inaccurate plans before coding agents are assigned tasks.

Agent for Claude Code

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

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

Good fit Use it before dispatching implementation work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ferroxlabs/ijfw/ijfw-plan-checker
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, 1 MCP server.

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-plan-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-plan-checker.svg)](https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-plan-checker)
Your own site
<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-plan-checker"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-plan-checker.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 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,103 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.00026 $0.01103
Opus 5 $0.00013 $0.00551
Sonnet 5 $0.00005 $0.00221
Haiku 4.5 $0.00003 $0.00110

Measured 7d ago against content hash 5e2a3e8318ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ijfw-plan-checker 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 7d 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-plan-checker.md · 113 lines

How it starts

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

Cross-reference every "NEW file" claim and "MODIFY " claim in the phase plan against the live codebase. Flag re-specs of existing infrastructure. v1.5.0's own HANDOFF was 60% re-spec of v1.4.x code -- this agent makes that visible at plan-time, not at execute-time.

ROLE

Pre-dispatch reality check. In v1.4.4's first handoff, half of the "new" work was actually already shipped in v1.4.3 (verifyFreshCommit existed, wave-state.js existed, blackboard.js existed). Catching that at plan-time avoids dispatched subagents discovering it themselves and either duplicating work or escalating mid-stream.

PROCESS

  1. Read the plan -- find .planning/<phase>/plan.md (or HANDOFF-.md; accept explicit input). Extract every:

    • NEW <path> declaration (string match on the word "NEW" followed by a path)
    • MODIFY <path> declaration
    • Bare path mentions in "Files: ..." headers (Wave plan convention)
    • Symbol mentions in `functionName` backtick code (heuristic -- high recall, lower precision; flag for review rather than block).
  2. For each NEW path, check existence via Glob:

    • If file already exists -> finding RESPEC_NEW.
    • If parent dir exists but file doesn't -> finding OK_NEW.
    • If no parent dir -> finding OK_NEW_GREENFIELD.
  3. For each MODIFY path, check existence:

    • File doesn't exist -> finding MISSING_MODIFY (the plan wants to modify a non-existent file; likely typo or upstream re-spec).
    • File exists -> finding OK_MODIFY (no further validation; this agent can't grade modification scope).
  4. For each backtick-symbol, grep across mcp-server/src/, claude/, installer/. If found -> EXISTING_SYMBOL <file:line> finding for human review. If not found -> no finding (could be a NEW symbol or noise).

  5. Write .planning/<phase>/PLAN-CHECK.md:

    # Plan Check -- <phase>
    
    ## Re-specs of existing infrastructure
    | declared_as | actual_status | existing_path | recommendation |
    |---|---|---|---|
    | NEW mcp-server/src/foo.js | EXISTS | mcp-server/src/foo.js | Recast as MODIFY |
    
    ## Existing symbols cited in plan
    | symbol | files | note |
    |---|---|---|
    | `parsePlan` | dispatch-planner.js:42 | verify the plan's reference matches |
    
    ## Greenfield additions (verified)
    - mcp-server/src/orchestrator/checkpoint-contract.md
    
    ## Summary
    RESPEC_NEW: N  MISSING_MODIFY: N  EXISTING_SYMBOL: N  OK: N
    

Read the full file on GitHub · 113 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. 7d ago First seen · 113 lines · 26 tokens per session scan A 5e2a3e8318ae

Subscribe to this mod's changes

ijfw-plan-checker is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 1,103 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-30.