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 agentmods add commands/ferroxlabs/ijfw/ijfw-helpgit 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/commands/ferroxlabs/ijfw/ijfw-help)<a href="https://agentmods.dev/commands/ferroxlabs/ijfw/ijfw-help"><img src="https://agentmods.dev/badge/commands/ferroxlabs/ijfw/ijfw-help.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00050 | $0.00383 |
| Opus 5 | $0.00025 | $0.00192 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
ijfw-help 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 4d 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
Dispatch the IJFW guide to the user.
Detect intent
- If the user passed
--browser(or asked for "browser", "render", "pretty view") runijfw help --browserin a Bash tool call. This renders the guide as HTML at~/.ijfw/guide/index.htmland opens it in the default browser. - Otherwise, run
ijfw helpin a Bash tool call. The guide prints to terminal paged throughless -R.
If the user is asking a scoped question (not "open the guide")
Examples: "how do I run a cross audit?", "what does ijfw memory recall do?", "what are the workflow modes?".
Do NOT open the full guide. Instead:
- Read
docs/GUIDE.mdfrom the repo root (fallback:~/.ijfw/docs/GUIDE.md). - Grep for the section the user asked about.
- Quote the relevant block (command reference row, FAQ entry, or quickstart win) in your reply. Keep it under 20 lines.
- Offer: "Full guide:
ijfw help --browserfor the rendered version, orijfw helpin the terminal."
Never
- Never invent commands that are not in
docs/GUIDE.md. - Never paraphrase the guide when the user asked a direct "how do I" question. Quote the real command.
- Never open the browser without user intent. If unsure, print the terminal version first and offer the browser option.
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.
- 4d ago First seen · 29 lines · 50 tokens per session scan A ee60cc7a4069
ijfw-help is a command published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 11d ago), licensed MIT. It adds 50 tokens to every session and 383 once invoked, about $0.0003 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.
Other commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
meta-theory-verify
Run the appropriate MetaKim verification path.
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
resolve-conflicts
Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.
implement
Execute implementation by processing atomic task files one at a time with Context Pinning (Atomic Traceability Model).