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.
git clone --depth 1 https://github.com/jaycewalzer1/SilverKey-Inc.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.
[](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./folder-decomposition)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./folder-decomposition"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./folder-decomposition/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/rules/jaycewalzer1/silverkey-inc./folder-decomposition"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./folder-decomposition.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.00000 | $0.00778 |
| Opus 5.5 | $0.00000 | $0.00311 |
| Sonnet 5.5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
folder-decomposition 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Folder Decomposition Rules
When to Break a Folder Into Subfolders
A folder has too many files and should be considered for subfolders when:
- File count: The directory contains more than ~10–15 files (or more than ~8–10 if they are all same-type, e.g. all components).
- Mixed concerns: Files fall into clear groups (e.g. by feature, by type, or by domain) that can each live in a subfolder.
- Discoverability: The flat list is hard to scan or navigate.
You may move some files into subfolders and leave others at the current level (e.g. an index.ts, a main entry, or a few shared files).
How to Decompose
- Identify groups: Group files by concern (feature, type, or domain). Name subfolders accordingly (e.g.
components/,hooks/,sections/, or domain names). - Move files: Move only the files that belong in each subfolder. Keep a barrel (
index.ts/__init__.py) at the parent if it helps preserve existing public API. - Preserve public API where useful: Prefer re-exporting from the parent (e.g. parent
index.tsre-exports from subfolders) so external imports can stay on the parent path if desired. Otherwise, update all imports (see below).
Required: Update All Imports
After moving files, you must complete both steps below. Do not leave broken or outdated imports.
Step 1: Update imports inside moved files
- Fix relative imports in each moved file so they still resolve correctly (e.g.
../utils→../../utilsor./utilsinside the new subfolder). - Fix same-folder references (e.g.
./sibling→./siblingif both moved, or adjust to new relative path). - Fix barrel or parent imports (e.g. from
../indexor parent modules) to match the new paths.
Step 2: Scan the codebase for imports from old paths and update
- Search the entire codebase for imports that reference the old file paths or the old folder (e.g.
from features/feed/Reels/SomeFileorfrom ./OldLocation/component). - Update every such import to the new path (e.g.
from features/feed/Reels/components/SomeFileor the new subfolder path). - Check:
- All
import/require(TS/JS) orimport/from(Python). - Barrel files (
index.ts,__init__.py) that re-export moved modules. - Config or test files that reference the moved modules.
- All
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 · 55 lines · 0 tokens per session scan A 87362a2aa940
folder-decomposition is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 778 tokens. 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.