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/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/comprehensiveness-over-simplification)<a href="https://agentmods.dev/rules/arango-solutions/arango-sparql-py/comprehensiveness-over-simplification"><img src="https://agentmods.dev/badge/rules/arango-solutions/arango-sparql-py/comprehensiveness-over-simplification.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.1 | $0.00487 | $0.00487 |
| Opus 5 | $0.00244 | $0.00244 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
comprehensiveness-over-simplification 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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensiveness Over Simplification
"If a feature ships incomplete, it didn't ship—it leaked."
You are building production systems. Simplification is the enemy of completeness.
Completeness Dimensions
Every piece of work must address ALL of the following. Skipping any is a defect.
Error Handling
- No swallowed errors — every
catch/if err != nilmust DO something - Descriptive messages — WHAT failed, WITH WHAT input, WHY
- Context wrapping —
fmt.Errorf("loading config: %w", err) - Graceful degradation over crashing
Edge Cases
Every function must handle: empty/nil inputs, boundary values, invalid inputs, unicode/special chars, concurrent access.
Configuration Over Hardcoding
If a value could EVER differ across dev/staging/prod, it must be configurable.
Test Completeness
Cover: happy path, error paths, edge cases, concurrency, regressions.
Observability
Structured logging (not fmt.Println), metrics, tracing, health checks, alertable events.
Security
Input validation at boundaries, no secrets in code/logs, auth/authz checks, least privilege.
Documentation
Public function docstrings, README updates, API docs with examples, architecture notes for non-obvious decisions.
UI/UX (Frontend)
Handle: loading, error, empty, success states. Accessibility (ARIA, keyboard nav). Responsive design.
Data Integrity
Validate at boundaries, database constraints, transaction safety, idempotency.
Performance
Pagination, caching, lazy loading, indexing, connection pooling.
Anti-Patterns (NEVER Do)
| Anti-Pattern | Consequence |
|---|---|
| Happy Path Only | Production incidents |
| "We'll Add That Later" | "Later" never comes |
| Empty Catch Blocks | Hidden failures |
| Magic Numbers | Unmaintainable code |
| Copy-Paste Coding | Divergent behavior over time |
| Console.log Debugging | Noise in production logs |
The Mantra
"Complete is better than clever. Robust is better than fast. Production-ready is the only ready."
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.
- 7d ago First seen · 65 lines · 487 tokens per session scan A ca3a77a4ce57
comprehensiveness-over-simplification is a cursor rule published in the GitHub repository arango-solutions/arango-sparql-py (2 stars, last pushed today), licensed MIT. It adds 487 tokens to every session, about $0.0024 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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.