Borrowing it
Nothing to install: this file belongs to FerroxLabs/ijfw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FerroxLabs/ijfw/main/AGENTS.mdgit 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/instructions/ferroxlabs/ijfw/agents-md)<a href="https://agentmods.dev/instructions/ferroxlabs/ijfw/agents-md"><img src="https://agentmods.dev/badge/instructions/ferroxlabs/ijfw/agents-md/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/instructions/ferroxlabs/ijfw/agents-md"><img src="https://agentmods.dev/badge/instructions/ferroxlabs/ijfw/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.05150 | $0.05150 |
| Opus 5.5 | $0.02060 | $0.02060 |
| Sonnet 5.5 | $0.01030 | $0.01030 |
| Haiku 4.5 | $0.00515 | $0.00515 |
Grade A, and why
ijfw AGENTS.md 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.
What it actually says
AGENTS.md
This file follows the open AGENTS.md spec (https://agents.md/) and is the canonical agent-instructions surface for this project. Platform-specific files (CLAUDE.md, GEMINI.md, WAYLAND.md, codex/AGENTS.md, .cursorrules, .windsurfrules, copilot-instructions.md) are thin adapters that point here.
Four IJFW-managed regions live in this file. Content outside the markers is yours -- IJFW will never touch it.
Project memory at .ijfw/memory/. Call ijfw_memory_prelude for full context.
Last handoff: IJFW 1.3.2 RC audit/verify pass is complete locally. The 1.3.1 release caution still applies: user explicitly said, "When windows completes and verifies we go forward. Remember that". Do NOT create/push tags or attempt npm publish until Windows CI/release clearance is explicitly given by the user. Current 1.3.2 verification has passed 880/880 Node tests, 158/158 focused regression tests, package dry-runs, temp-project swarm E2E, cross-audit reconciliation, platform drift, diff hygiene, and preflight blocking gates. Findings fixed during audit: hermetic update-confirm npm test PATH, Trident EPIPE hardening, workflow bootstrap/fallback guidance, team/AGENTS mirroring specificity, Codex dispatch command order, and memory/release-gate consistency. Advisory warnings only: eslint-security non-literal fs warnings in installer paths and PSScriptAnalyzer skipped because pwsh unavailable locally. No tag or publish performed.
No project agents yet. Run ijfw team to set them up.
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 · 694 lines · 5,150 tokens per session scan A 6a10e0376bc2
ijfw AGENTS.md is an instructions file published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 5d ago), licensed MIT. It adds 5,150 tokens to every session, about $0.0206 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).