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.
npx agentmods add rules/arango-solutions/arango-sparql-py/modularity-and-structuregit clone --depth 1 https://github.com/arango-solutions/arango-sparql-pyWrote 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/arango-solutions/arango-sparql-py/modularity-and-structure)<a href="https://agentmods.dev/rules/arango-solutions/arango-sparql-py/modularity-and-structure"><img src="https://agentmods.dev/badge/rules/arango-solutions/arango-sparql-py/modularity-and-structure.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 | $0.00366 | $0.00366 |
| Opus 5 | $0.00183 | $0.00183 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
modularity-and-structure 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 3d 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.
What it actually says
Modularity and Structure
"Everything has a place. Put everything in its place."
File Size Limits
| File Type | Max Lines | Action If Exceeded |
|---|---|---|
| Source code | 1500 | Split into multiple files |
| Test files | 2000 | Split by test category |
| Config files | 500 | Use includes/imports |
| Documentation | 1000 | Split into sections |
Signs a File Needs Splitting
- Can't find things without search
- Multiple unrelated concerns
- Multiple people need to edit it simultaneously
File Placement Rules
| File Type | Goes In | NOT In |
|---|---|---|
| Shared types | Core/types module | Random location |
| Tests | Next to source file | Separate tests/ folder (except E2E) |
| Configs | configs/ |
Root directory |
| Scripts | scripts/ |
Root directory |
Module Cohesion
Each package/module should:
- Have a single responsibility
- Expose a minimal public API
- Hide implementation details
- Be independently testable
Before Creating Any File
| Check | Question |
|---|---|
| Location | Is this the right directory? |
| Naming | Does the name follow existing conventions? |
| Size | Will this file stay under limits? |
| Cohesion | Does this file belong with its neighbors? |
| Discoverability | Can someone find this file intuitively? |
A new developer should be able to find any file based solely on what it does, without searching.
Structure is not bureaucracy—it's navigation.
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.
- 3d ago First seen · 54 lines · 366 tokens per session scan A c7e9e58fd8f3
modularity-and-structure is a cursor rule published in the GitHub repository arango-solutions/arango-sparql-py (2 stars, last pushed 17d ago), licensed MIT. It adds 366 tokens to every session, about $0.0018 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-31.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.