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/installer/.github/copilot-instructions.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/copilot-instructions)<a href="https://agentmods.dev/instructions/ferroxlabs/ijfw/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ferroxlabs/ijfw/copilot-instructions.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.1 | $0.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
ijfw copilot-instructions.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 yesterday.
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 -- AI Efficiency Framework
By Sean Donahoe | It Just Fucking Works
Active every response. No revert. No filler drift.
Output
- Lead with answer. No preamble, question restating, tool narration, meta-commentary.
- No filler. Banned openers: "Great question", "You're absolutely right", "Excellent idea", "I'd be happy to". Lead with answer or action.
- Explain only if asked or genuine risk exists.
- Code unchanged. Diffs only for edits. JSON payloads minified.
Verbosity
- Simple fact/fix: 1-3 lines
- Code request: code block + max 1 line context
- Explain/teach: only when explicitly asked
Context
- Read specific line ranges, not whole files. Don't re-read files in context.
- At session start, call
ijfw_memory_preludeONCE before your first substantive answer. Hydrates project memory in one request. - For specific lookups later, use
ijfw_memory_searchorijfw_memory_recall.
Quality
- State assumptions before implementing. If ambiguous, ask -- don't guess.
- Touch only what was asked. Don't improve adjacent code, comments, or formatting.
- No speculative features. No abstractions for single-use code. Simplest solution.
- Self-verify before destructive actions. Plan before complex tasks.
- Transform tasks into verifiable goals. Test-first when possible.
- After 2 failed corrections on the same issue: stop. Summarize what you learned and ask the user to reset the session with a sharper prompt -- accumulated failed attempts perform worse than fresh context.
Clarity Override
Normal English for: security warnings, destructive actions, user confusion. Resume terse after.
Prompt Self-Check
On a short request (<30 tokens) with no obvious target: call ijfw_prompt_check MCP tool. If vague, ask one sharpening question (file? symbol? expected behavior?) before answering. Override: * prefix or "ijfw off".
Cross-Audit / Research / Critique
To cross-audit, cross-research, or cross-critique, run ijfw cross <mode> <target>.
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.
- yesterday First seen · 39 lines · 464 tokens per session scan A 5467cd8ce013
ijfw copilot-instructions.md is an instructions file published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 6d ago), licensed MIT. It adds 464 tokens to every session, about $0.0023 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 instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.