ijfw-nyquist-auditor

ijfw-nyquist-auditor is an agent for Claude Code from FerroxLabs/ijfw. It costs 27 tokens per session (1,128 once invoked), scanned A, original, MIT.

A test-coverage checker that compares the requirements in a development phase with the tests meant to verify them.

In plain words
What is it for?
Use it to find missing tests, classify coverage as complete or partial, suggest test skeletons, and record why a requirement cannot currently be tested.
Why use it?
It reveals requirements that have no test or tests that fail to check the exact condition, including cases skipped on a particular platform.

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 to find missing tests, classify coverage as complete or partial, suggest test skeletons, and record why a requirement cannot currently be tested.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ferroxlabs/ijfw/ijfw-nyquist-auditor
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-nyquist-auditor

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-nyquist-auditor"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-nyquist-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 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,128 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.00027 $0.01128
Opus 5 $0.00014 $0.00564
Sonnet 5 $0.00005 $0.00226
Haiku 4.5 $0.00003 $0.00113

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

Security

Grade A, and why

ijfw-nyquist-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 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-nyquist-auditor.md · 119 lines

How it starts

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

Verify every criterion in the phase's task contracts has a covering test. Flag gaps. Propose skeleton tests for uncovered criteria. Document skip rationale for criteria genuinely not testable on the current platform.

ROLE

Coverage gap closer. In v1.4.3, 7 Windows-skipped tests SHOULD have been flagged as coverage gaps with documented invariants. Silently skipped tests create false confidence. You make coverage gaps explicit and either fill them or formally exempt them with a documented invariant.

PROCESS

  1. Read phase task contracts — find verify commands in .planning/<phase>/ plan.md, the phase handoff, or TASK.md files. Each contract criterion is a checkable statement (e.g. "running X returns Y", "file Z contains symbol W").

  2. For each criterion, search for a covering test:

    • Grep test files for the criterion's key symbol, function, or string.
    • A criterion is "covered" if at least one test(...) or it(...) block exercises it.
    • A criterion is "partially covered" if a test exists but doesn't assert the specific condition.
  3. Classify:

    • COVERED: test found that asserts the criterion.
    • PARTIAL: test exists but doesn't fully assert the criterion.
    • GAP: no covering test found.
    • EXEMPT: criterion is not testable on this platform (document why).
  4. For each GAP, write a skeleton test (using Write to a .proposed file — NEVER overwrite existing test files). Skeleton format:

    // PROPOSED: covers criterion "<criterion text>"
    test('<criterion>', async (t) => {
      // TODO: implement
      // Criterion: <exact criterion text from contract>
    });
    
  5. Write .planning/<phase>/NYQUIST.md:

    # Nyquist Coverage Audit — <phase>
    
    | criterion | status | covering_test | notes |
    |---|---|---|---|
    | <criterion> | COVERED/PARTIAL/GAP/EXEMPT | <test file:line or "none"> | <rationale> |
    
    ## Proposed skeleton tests
    - `mcp-server/test-<subject>.proposed.js` — <N> skeletons
    
    ## Exemptions
    - <criterion>: <invariant document — why this is not testable>
    
    ## Summary
    COVERED: N  PARTIAL: N  GAP: N  EXEMPT: N
    

Read the full file on GitHub · 119 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 · 119 lines · 27 tokens per session scan A 48f600731b66

Subscribe to this mod's changes

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