Borrowing it
Nothing to install: this file belongs to AmanKtyr/Tailor. 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/AmanKtyr/Tailor/main/.windsurfrulesgit clone --depth 1 https://github.com/AmanKtyr/TailorWrote 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/rules/amanktyr/tailor/windsurfrules)<a href="https://agentmods.dev/rules/amanktyr/tailor/windsurfrules"><img src="https://agentmods.dev/badge/rules/amanktyr/tailor/windsurfrules.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.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidance (Powered by Tailor)
This repository uses Tailor for project intelligence, Spec-Driven Development, and Reuse-First engineering discipline.
Non-Negotiable Directives
1. Cold-Start & Project Memory Hierarchy
- Always consult
.ai/CONSTITUTION.mdand.ai/INDEX.mdfirst before planning or making non-trivial modifications. - Cold-Start Fallback: If the
.ai/directory does not exist yet, do NOT invent arbitrary conventions. Inspectpackage.json(or workspace manifests) and active source files directly to determine established patterns, and suggest runningnpx @amanktyr/tailor initto establish project memory.
2. Mandatory Guardrail: Zero Unrequested Styling & Redesign
- STRICTLY PROHIBITED: NEVER add, alter, or inject CSS, styling frameworks, inline styles, gradients, glassmorphism, or animations unless the user explicitly requested visual or styling changes.
- When working on logic, bugfixes, refactoring, or state management: preserve existing visual markup and styling tokens untouched.
- When writing UI components: strictly reuse existing design tokens, components, and CSS classes from the codebase or
.ai/UI.md. Never invent new arbitrary classes, hex colors, or custom styling rules. - If the project has no styling system and no styling is requested, output clean, unstyled semantic HTML.
3. Mandatory Guardrail: Zero Bloat & Minimal Diff Discipline (Anti-Slop)
- Implement only the minimal code required to satisfy the user's specific request.
- NO speculative abstractions: Do not create premature wrapper classes, generic factories, or speculative interfaces for one-off operations.
- NO dummy/mock data: Never add mock datasets, fake user lists, or placeholder fixtures in production code.
- NO filler comments: Never write redundant explanatory comments (e.g.
// Here we define the function) that state the obvious. Only document why non-obvious business logic or security decisions exist.
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.
- today First seen · 36 lines · 689 tokens per session scan A 75d53c701b29
windsurfrules is a cursor rule published in the GitHub repository AmanKtyr/Tailor (3 stars, last pushed today), licensed MIT. It adds 689 tokens to every session, about $0.0034 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-06.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
A modular system for recording project context, decisions, requirements, and lessons in structured files. It divides the recorder into core, template, advanced, and edge-case modules.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.