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.
npx skills add FerroxLabs/ijfw --skill ijfw-doctorgit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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.
[](https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-doctor)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-doctor"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-doctor/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.
<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-doctor"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
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 Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00025 | $0.00433 |
| Opus 5 | $0.00013 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
ijfw-doctor 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 5d 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.
What it actually says
IJFW Doctor
Run each check silently, then emit a single positive-framed report. Never say "failed", "error", or "not found" -- reframe every finding as an action or a ready state.
Checks (run in order)
1. MCP Server
Call ijfw_metrics. If it responds: "Memory server active". If unreachable: "Memory server ready to connect -- run claude mcp add ijfw-memory node /path/to/mcp-server/src/index.js".
2. Memory Directory
Check .ijfw/memory/ exists and is writable (test -w .ijfw/memory). If writable: "Memory directory writable". If missing: "Memory directory ready to create -- first memory write will initialize it".
3. Hooks
Check for hook scripts in the platform's hooks directory (e.g. ~/.claude/hooks/ for Claude, .codex/hooks/ for Codex). If scripts exist and are executable: "Hooks registered and live". If missing: "Hooks standing by -- re-run install.sh to register".
4. Platform Integration Depth
Report which features are active based on what's detected:
- MCP connected = deep integration
- Hooks present = prompt sharpener active
- Memory populated = context carry-over active
- Config present = custom rules loaded
5. Node.js Version
Run node --version. If 18+: "Runtime ready (Node )". If missing or older: "Node.js 18+ needed -- install from https://nodejs.org".
Format
5-line list, one line per check, all positive. End with:
All systems active -- IJFW running at full depth.
Or if any items need action:
IJFW active -- <N> of 5 systems at full depth. Steps above complete the setup.
Under 20 lines total. No negatives.
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.
- 5d ago First seen · 42 lines · 25 tokens per session scan A d1e66bdf15ef
ijfw-doctor is a skill published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 433 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-09-05.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
bug-fixer
name: bug-fixer description: Used when the user says "this feature is broken", "getting an error", "something's not right", or reports a bug, compilation error, or runtime exception. Locates root cause through a four-stage systematic debugging process and fixes it. version: 1.2.0 updated: 2026-06-27 requires: [].
reqforge-greenkeeper
name: reqforge-greenkeeper description: Used when maintaining the ReqForge repository itself and its release gates fail — pnpm test, pnpm forge-smoke, pnpm sync:discover, adapter drift, skill fixtures, loadouts, or test-demo golden path. Restores a green, synced state with minimal changes. Not for bugs in user apps…
debugger
Finds the root cause of a defect hypothesis-first: reproduce it, form competing hypotheses, gather evidence that discriminates between them, then fix the cause and prove the fix. Use when a test fails for unclear reasons, a failure is flaky or happens only in CI, behaviour differs from what was expected, or a…