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/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/code-organization)<a href="https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/code-organization"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/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/bilal140202/the-lord-of-the-skills/code-organization"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/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.01948 | $0.01948 |
| Opus 5 | $0.00974 | $0.00974 |
| Sonnet 5 | $0.00390 | $0.00390 |
| Haiku 4.5 | $0.00195 | $0.00195 |
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 9d 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.
This is a copy
100% identical to code-organization — 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.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Organization
Project Folder Structure
Assets/
├── !_Project/ # Main project content (! keeps it at top)
│ ├── Art/
│ │ ├── Materials/
│ │ ├── Models/
│ │ ├── Textures/
│ │ └── Animations/
│ ├── Audio/
│ │ ├── Music/
│ │ ├── SFX/
│ │ └── Mixers/
│ ├── Prefabs/
│ │ ├── Characters/
│ │ ├── Environment/
│ │ ├── UI/
│ │ └── Effects/
│ ├── Scenes/
│ │ ├── Levels/
│ │ ├── Menus/
│ │ └── Test/
│ ├── Scripts/
│ │ ├── Runtime/ # Runtime code
│ │ │ ├── Core/ # Base systems
│ │ │ ├── Gameplay/ # Game logic
│ │ │ ├── UI/ # UI controllers
│ │ │ ├── Utilities/ # Helper classes
│ │ │ ├── DOTS/ # ECS implementation
│ │ │ │ ├── Components/ # IComponentData
│ │ │ │ ├── Systems/ # SystemBase/ISystem
│ │ │ │ └── Aspects/ # Aspects
│ │ │ └── Hybrid/ # Mixed MonoBehaviour + DOTS
│ │ ├── Editor/ # Editor scripts
│ │ └── Tests/ # Test assembly scripts
│ ├── ScriptableObjects/
│ │ ├── GameConfig/ # Game settings
│ │ ├── EventChannels/ # SO-based events
│ │ ├── Variables/ # Runtime shared data
│ │ ├── Sets/ # SO Sets for collections
│ │ └── Stats/ # Character/weapon data
│ └── Settings/ # Project settings
├── Packages/ # Custom packages
│ └── com.yourcompany.core/ # Reusable modules
│ ├── Runtime/
│ ├── Editor/
│ ├── Tests/
│ └── Documentation~/
├── AddressableAssets/ # Addressables content
│ ├── Groups/ # Addressable Groups configs
│ ├── Settings/ # Addressable Settings
│ └── Content/ # Organized by strategy
│ ├── PerLevel/ # Concurrent usage strategy
│ ├── Characters/ # Logical entity strategy
│ └── Shared/ # Shared resources
├── Plugins/ # Third-party plugins
├── Tests/ # Test assemblies
│ ├── EditMode/
│ │ ├── Unit/ # Unit tests
│ │ └── Integration/ # Integration tests
│ ├── PlayMode/
│ │ ├── Functional/ # Functional tests
│ │ └── Performance/ # Profiling tests
│ └── TestUtilities/ # Common mocks and helpers
└── TextMesh Pro/ # TMP resources
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.
- 9d ago First seen · 282 lines · 1,948 tokens per session scan A d12b7b8e4e32
code-organization is a cursor rule published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 1,948 tokens to every session, about $0.0097 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-organization, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
security
Security rules for all source files.
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.
cli-error-handling
CLI command error handling patterns.
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.