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/sijeeshmiziha/visionagentWrote 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/sijeeshmiziha/visionagent/design-patterns)<a href="https://agentmods.dev/rules/sijeeshmiziha/visionagent/design-patterns"><img src="https://agentmods.dev/badge/rules/sijeeshmiziha/visionagent/design-patterns/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/sijeeshmiziha/visionagent/design-patterns"><img src="https://agentmods.dev/badge/rules/sijeeshmiziha/visionagent/design-patterns.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.00894 | $0.00894 |
| Opus 5.5 | $0.00358 | $0.00358 |
| Sonnet 5.5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
design-patterns 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Patterns and Code Organization
File Size Limit: 150 Lines Maximum
Every source file must contain at most 150 lines of code.
- Enforces Single Responsibility and keeps files navigable.
- When a file grows toward the limit, split before adding more.
- Splitting strategies: Extract interfaces to
*.interface.tsortypes.ts; move helpers to*.utils.ts; split a class into a base in one file and concrete impl in another; one pattern/feature per file.
Pattern Selection
| Pattern | Use When | Avoid When |
|---|---|---|
| State | Behavior varies by internal state; replacing switch/case on state | Simple flags; few states |
| Strategy | Interchangeable algorithms at runtime | Single algorithm |
| Chain of Responsibility | Multiple handlers may process a request; dynamic chains | Single handler; fixed flow |
| Builder | Complex object, many optional parts, step-by-step construction | Simple objects; few params |
| Observer | Multiple listeners for the same events | Single consumer |
| Decorator | Add/stack behaviors dynamically (retry, log, cache) | Static, single behavior |
| Factory Method | Creation delegated to callers; varying product types | One product type; simple new |
State vs Strategy
- State: Context has a current state; state object handles requests and may transition context to another state. Use for stage machines, wizards, workflows (e.g. discovery → requirements → design).
- Strategy: Context delegates an algorithm to a strategy; no notion of "current state" or transitions. Use for swapping sort/search/format logic.
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 · 96 lines · 894 tokens per session scan A cb3370a76580
design-patterns is a cursor rule published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 7mo ago), licensed MIT. It adds 894 tokens to every session, about $0.0036 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-31.
Other cursor rules, from other repositories
solidity-foundry-cursorrules-prompt-file
Cursor rule "solidity-foundry-cursorrules-prompt-file" from ItamarZand88/awesome-agent-conventions, covering do not compile tests when compiling via-ir and don't pollute bytecode with metadata.
grug-brained-dev_simple-tools
Choose tools and libraries that are simple and well-understood.
160-workflow-orchestration
WHEN executing tasks MANAGE workflow processes for consistent memory operations.
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.
050-reference-verification-system
description: WHEN referencing memory files ENSURE references are verified for accuracy and relevance globs: ["/.md", "/.mdc"] alwaysApply: true.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.