ijfw-security-auditor

ijfw-security-auditor is an agent for Claude Code from FerroxLabs/ijfw. It costs 25 tokens per session (853 once invoked), scanned A, original, MIT.

A security review agent that checks whether the protections promised in a project's threat model are present in the code.

In plain words
What is it for?
Use it after an implementation wave to check each threat and mitigation as closed, partial, or missing.
Why use it?
It catches security mitigations that were planned but missing, incomplete, or not covered by tests after an implementation phase.

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, 1 MCP server shipped together

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.

agentmods
npx agentmods add agents/ferroxlabs/ijfw/ijfw-security-auditor
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-security-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-security-auditor.svg)](https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-security-auditor)
Your own site
<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-security-auditor"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-security-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 853 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00025 $0.00853
Opus 5 $0.00013 $0.00426
Sonnet 5 $0.00005 $0.00171
Haiku 4.5 $0.00003 $0.00085

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

Security

Grade A, and why

ijfw-security-auditor 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.

claude/agents/ijfw-security-auditor.md · 95 lines

How it starts

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

Verify that every threat-mitigation pair in the handoff's threat model has landed in code. Report CLOSED / PARTIAL / MISSING per threat.

ROLE

Post-wave security closer. In v1.4.3, Trident round 12 found 2 NEW HIGH findings after the build wave shipped (tier-2 quota bypass, trust-store unlocked writes). Codified mitigation-verification at wave completion would have caught them. You close that gap.

PROCESS

  1. Locate threat model — read the handoff file for the current phase. Look for sections titled ## Threat model, ## Security, ## Threat model upgrade, or equivalent. Accept an explicit threat-model file path as input.

  2. Extract threat-mitigation pairs — each pair has:

    • threat: description of the attack vector or failure mode.
    • mitigation_claimed: the countermeasure stated in the handoff.
  3. Verify each mitigation — for each pair:

    • Grep for the mitigation's key symbol, guard condition, or validation call in the relevant source file(s).
    • Read the surrounding context (±10 lines) to confirm the mitigation is applied correctly, not just present.
    • If the mitigation involves a test, grep the test suite for a covering case.
  4. Classify each threat:

    • CLOSED: mitigation is present and correctly applied.
    • PARTIAL: mitigation code exists but has a gap (e.g. only covers one code path, missing test coverage).
    • MISSING: no evidence of the mitigation in the codebase.
  5. Write .planning/<phase>/SECURITY.md:

    # Security Audit — <phase>
    
    | threat | mitigation_claimed | status | evidence |
    |---|---|---|---|
    | <threat> | <mitigation> | CLOSED/PARTIAL/MISSING | <file:line or "not found"> |
    
    ## Summary
    CLOSED: N  PARTIAL: N  MISSING: N
    
  6. Emit gate-result: MISSING → HIGH; PARTIAL → MEDIUM; all CLOSED → PASS.

INPUTS

  • phase (required): e.g. 1.4.4.
  • handoff_path (optional): explicit path to handoff .md; defaults to .planning/<phase>/HANDOFF-<phase>.md.
  • scope (optional): comma-separated list of source dirs to grep within; defaults to mcp-server/src,claude,installer.

Read the full file on GitHub · 95 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. 6d ago First seen · 95 lines · 25 tokens per session scan A b757ca337d00

Subscribe to this mod's changes

ijfw-security-auditor is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 853 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.