folder-boundaries

A folder-organization rule for keeping features, view models, services, and data models in their designated places. Folder boundaries are the agreed limits on where each kind of code may live.

In plain words
What is it for?
Use it when adding or reviewing files in projects that separate feature code, screen logic, services, and models.
Why use it?
It prevents related code from being scattered across the project and makes the codebase easier to navigate and maintain.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/homebrew/brewui/folder-boundaries
Clone the repo
git clone --depth 1 https://github.com/Homebrew/BrewUI

Made for: Cursor.

Per session 181 This file is loaded in full into every session.
When invoked 181 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found 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 $0.00181 $0.00181
Opus 5 $0.00090 $0.00090
Sonnet 5 $0.00036 $0.00036
Haiku 4.5 $0.00018 $0.00018

Measured yesterday against content hash c1bf58e36afa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

folder-boundaries 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.

.cursor/rules/folder-boundaries.mdc · 14 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. yesterday First seen · 14 lines · 181 tokens per session scan A c1bf58e36afa

Subscribe to this mod's changes

folder-boundaries is a cursor rule published in the GitHub repository Homebrew/BrewUI (119 stars, last pushed yesterday), licensed AGPL-3.0. It adds 181 tokens to every session, about $0.0009 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.