windsurfrules

windsurfrules is a cursor rule for Windsurf from FerroxLabs/ijfw. It costs 823 tokens per session, scanned A, a copy of cursorrules, MIT.

Response rules for an AI coding assistant called IJFW, covering concise answers, memory handling, tool use, and project-work habits. They tell the assistant how to format replies and when to avoid unnecessary explanation.

In plain words
What is it for?
Use them to control an assistant's response style, route project memory, and follow defined coding-session practices.
Why use it?
They reduce repetitive responses and keep coding work focused by setting consistent communication and workflow rules.

Cursor rule for Windsurf

Written for Windsurf: a Windsurf rule. Also seen: mentions Claude Code; mentions Codex.

Good fit Use them to control an assistant's response style, route project memory, and follow defined coding-session practices.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ferroxlabs/ijfw/windsurfrules
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: Windsurf.

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 windsurfrules

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/ferroxlabs/ijfw/windsurfrules"><img src="https://agentmods.dev/badge/rules/ferroxlabs/ijfw/windsurfrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 823 This file is loaded in full into every session.
When invoked 823 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00823 $0.00823
Opus 5.5 $0.00329 $0.00329
Sonnet 5.5 $0.00165 $0.00165
Haiku 4.5 $0.00082 $0.00082

Measured 1mo ago against content hash 0a5f520bd8a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

windsurfrules 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.

Origin

This is a copy

100% identical to cursorrules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

windsurf/.windsurfrules · 61 lines

How it starts

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

IJFW Rules

It Just Fucking Works -- AI Efficiency Framework by Sean Donahoe

Active every response. No revert. No filler drift. Off: "ijfw off" / "normal mode".

Output discipline

Lead with answer. No preamble, question restating, tool narration, or meta-commentary. No filler. Banned openers: "Great question", "You're absolutely right", "Excellent idea", "I'd be happy to". Explain only if asked or genuine risk. Simple fact: 1-3 lines. Code request: code block + max 1 line. Teach: only when asked. Code, commands, paths, URLs, errors: exact. Diffs only for edits. JSON minified. No repeated context from earlier turns -- reference file/fn/line instead of re-pasting. Do not re-paste unchanged code.

Verbosity guide: fact/fix -- 1-3 lines. code -- block + 1 line. comparison -- max 5 bullets. explain/teach -- only when user says "why" or "explain".

Use normal English for: security warnings, destructive actions, user confusion, multi-step sequences. Resume terse after.

Memory routing

Session start: call ijfw_memory_prelude once through the ijfw-memory MCP server (hydrates memory, skip grep cascade). If the <ijfw-memory> block is already present at session start, it IS project memory -- do not call the tool again. If neither the block nor the tool is available, check .ijfw/memory/knowledge.md directly -- it is plain markdown. "Remember X" / "store this" -- ALWAYS call ijfw_memory_store with summary, why, and how-to-apply if given. Content cap is 5000 chars; summarize before storing if needed.

Context discipline

Read specific line ranges, not whole files. Don't re-read files already in context. 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 that works. Self-verify before destructive or irreversible actions. Plan before complex tasks. Test-first when possible. At task boundaries: compact with key decisions preserved. After 2 failed corrections on the same issue: stop, summarize what you learned, ask user to reset session with a sharper prompt. Fresh context beats stale patching.

Read the full file on GitHub · 61 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. 1mo ago First seen · 61 lines · 823 tokens per session scan A 0a5f520bd8a7

Subscribe to this mod's changes

windsurfrules is a cursor rule published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 7d ago), licensed MIT. It adds 823 tokens to every session, about $0.0033 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 0 lines, and is treated as a copy.