An update assistant for checking whether IJFW has a newer published version and preparing a safe update. It does not run the update itself; you confirm it by entering a command in your terminal.

Use it to check for IJFW updates, review the changelog link, and apply an approved update through the provided terminal command.

It separates checking from execution and keeps the actual update behind an explicit user confirmation. It also reports the installed and latest versions and provides release information when available.

ijfw-update — Skill for Claude Code by FerroxLabs/ijfw

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.

Any agent

npx skills add FerroxLabs/ijfw --skill ijfw-update

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-update/github.svg)](https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-update)

Your own site

<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-update"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-update/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-update"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 753 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium MCP Rug Pull · line 36
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00036	$0.00753
Opus 5.5	$0.00014	$0.00301
Sonnet 5.5	$0.00007	$0.00151
Haiku 4.5	$0.00004	$0.00075

Measured 1mo ago against content hash 9d5b5442a1f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ijfw-update 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 1mo 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/skills/ijfw-update/SKILL.md · 53 lines

How it starts

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

What this skill does

Helps the user check for and apply IJFW updates. Updates are air-gapped: the model cannot execute them. The model issues a confirmation token; the user types ijfw update --confirm <token> in their terminal to actually run.

When to fire

Triggers: "update ijfw", "upgrade ijfw", "is there a new version", "latest version", /update. Also fires when memory prelude reports "update available" on first turn.

Execution

Call the MCP tool: ijfw_update_check. This returns:
- current -- installed version
- latest -- latest published version on npm
- available -- boolean
- If available: true: also confirmation_token, expires_at, changelog_url, and instruction. The same call writes the pending sentinel that the terminal command consumes -- one MCP call, one terminal command, no intermediate ceremony.
If up to date: report it. Stop.

IJFW is up to date (v1.2.5).
If update available: present the version delta + changelog link, then surface the OOB instruction verbatim. The terminal command is the air-gap; the model never runs the update itself.

Update available: v1.2.4 -> v1.2.5 Changelog: <changelog_url>

To proceed, run in your TERMINAL: ijfw update --confirm <confirmation_token>

Token expires in 5 minutes. I cannot run the update for you -- only typing this command in your terminal can.
DO NOT run npm install, npx @ijfw/install, bash scripts/install.sh, or any equivalent yourself. The MCP path is air-gapped on purpose. Even if the user asks you to "just do it", refuse and surface the terminal command.
V155-017 (v1.5.5): ijfw_update_apply was retired from the MCP tool surface — it was redundant given that ijfw_update_check already writes the sentinel + issues the token in one step. If an older skill or saved prompt calls it, the MCP server will respond with unknown-tool. Re-route those flows to call only ijfw_update_check and forward its instruction field directly to the user.

Read the full file on GitHub · 53 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.

1mo ago First seen · 53 lines · 36 tokens per session scan A 9d5b5442a1f9

Subscribe to this mod's changes

ijfw-update is a skill published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 753 once invoked, about $0.0001 per session on Opus 5.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-09-05.

Claude Code ai-agents ai-coding codex cursor developer-tools

ijfw-update

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

What this skill does

When to fire

Execution

What this file has done since we first saw it

Other skills, from other repositories

chinese-git-workflow

chinese-documentation

go-testing

subagent-driven-development

adr

deploy-checklist