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/raydeStar/sir-thaddeusWrote 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/raydestar/sir-thaddeus/god-objects)<a href="https://agentmods.dev/rules/raydestar/sir-thaddeus/god-objects"><img src="https://agentmods.dev/badge/rules/raydestar/sir-thaddeus/god-objects/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/raydestar/sir-thaddeus/god-objects"><img src="https://agentmods.dev/badge/rules/raydestar/sir-thaddeus/god-objects.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.00650 | $0.00650 |
| Opus 5.5 | $0.00260 | $0.00260 |
| Sonnet 5.5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
GOD-OBJECTS 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rule: Prevent God-Objects and Giant Files
Use this as a hard project rule for Cursor (and for any future AI edits).
Prime Directive
Never grow a “god-object” file.
If a file is becoming a central dumping ground (routing + policy + execution + parsing + state), you must split it into focused modules before adding more features.
Hard Limits (non-negotiable)
1) File size limit
- Max target: 500 lines per file.
- Absolute max: 800 lines.
If a change would push a file over 800 lines, Cursor must:
- Stop adding features to that file.
- Extract new code into a new file/module.
- Update the calling file to delegate.
Exception: auto-generated files only (must be clearly marked and excluded).
2) One responsibility per file
A file may own exactly one of these responsibilities:
- Routing / intent classification
- Policy gating / permissions
- Tool execution loop
- Deterministic utilities
- Memory retrieval / merge
- Guardrails / reasoning pipeline coordination
- UI / lifecycle / wiring
If a file begins owning 2+ responsibilities, Cursor must split it.
“God-Object” Smell Tests
If any are true, refactor immediately (no debate):
- The file imports modules from 3+ distinct subsystems (e.g., routing + memory + tool runner + UI).
- The file contains 3+ distinct sections separated by large comment banners.
- A single class has 10+ methods or 10+ private fields.
- The class name contains words like Orchestrator, Manager, Coordinator and it implements business logic instead of delegating.
Required Architecture Pattern
The Orchestrator Rule
The orchestrator/coordinator file must be thin:
- It may perform sequencing and response assembly.
- It may not contain regex heuristics, parsing logic, routing decisions, policy rules, or tool loop mechanics.
All logic must live behind interfaces:
IRouterIPolicyGateIToolLoopExecutorIMemoryContextProviderIGuardrailsCoordinatorIDeterministicUtilityEngine
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 · 110 lines · 650 tokens per session scan A 6e94f65bf99b
GOD-OBJECTS is a cursor rule published in the GitHub repository raydeStar/sir-thaddeus (15 stars, last pushed 10d ago), licensed Apache-2.0. It adds 650 tokens to every session, about $0.0026 per session on Opus 5.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-30.
Other cursor rules, from other repositories
honcho_rules
Honcho persistent memory — capture every conversation, recall past context, and build a growing model of the user. Activates on every conversation.
netllm
Route netllm install, editor connect, swarm, troubleshoot, PR/release, and macOS CI requests to project skills and docs.
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
lighter-safety
Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.
terminal-commands
Guidelines for generating terminal commands that ensure outputs are readable by Cursor agents.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.