Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jaycewalzer1/SilverKey-Inc.npx agentmods add rules/jaycewalzer1/silverkey-inc./code-organizationWrote 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./code-organization)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./code-organization"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-organization/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./code-organization"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-organization.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.02187 |
| Opus 5.5 | $0.00000 | $0.00875 |
| Sonnet 5.5 | $0.00000 | $0.00437 |
| Haiku 4.5 | $0.00000 | $0.00219 |
Grade A, and why
code-organization 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Organization Rules
File Size and Method Placement
Prefer New Files for Large Methods
When adding large methods or substantial functionality, PREFER creating new files over expanding existing files to very large sizes.
Guidelines:
-
✅ Create a new file when adding a method that:
- Exceeds ~100-150 lines of code
- Has complex logic with multiple responsibilities
- Would push an existing file over ~400-500 lines
- Is a distinct feature or capability that can be logically separated
-
✅ Extract to a new file when an existing file:
- Exceeds ~500 lines and you're adding more functionality
- Contains multiple distinct concerns that can be separated
- Has methods that are rarely used together
-
✅ Keep related functionality together when:
- Methods are tightly coupled and always used together
- The file is still under ~400 lines
- Splitting would create unnecessary indirection
File Organization Patterns
Frontend (TypeScript/React)
Services:
// ✅ CORRECT: Split large service into focused modules
// services/calendar/core/service.ts (main service)
// services/calendar/events/operations.ts (event operations)
// services/calendar/calendars/management.ts (calendar management)
// ❌ AVOID: Single massive service file
// services/calendar/service.ts (1000+ lines with everything)
Hooks:
// ✅ CORRECT: Separate hooks by concern
// hooks/data/useCalendarEvents.ts
// hooks/data/useCalendarPreferences.ts
// hooks/data/useCalendarAvailability.ts
// ❌ AVOID: Single hook file with multiple large hooks
// hooks/data/useCalendar.ts (500+ lines with all calendar hooks)
Components:
// ✅ CORRECT: Extract large components or logic; utilities live in packages
// packages/features/calendar/components/Calendar.tsx (main component)
// packages/features/calendar/components/CalendarView.tsx
// packages/utils/calendar/eventParsing.ts (utilities – not under apps/web)
// ❌ AVOID: Single massive component file
// features/calendar/Calendar.tsx (800+ lines with everything)
// ❌ AVOID: Standalone .ts utilities under apps/web/features or components
// features/calendar/utils/eventParsing.ts
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 · 264 lines · 0 tokens per session scan A 3ea347bc3017
code-organization 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 2,187 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.