design-patterns

A reference for common software design patterns, which are reusable approaches to recurring design problems. It covers patterns such as Factory, Builder, Strategy, Observer, Repository and Facade, including when not to use them.

In plain words
What is it for?
Recognising repeated design problems, selecting an appropriate pattern and checking whether a proposed pattern improves the code.
Why use it?
It helps developers choose a suitable structure for a problem without adding unnecessary complexity or forcing a pattern where it does not fit.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/andr-ca/agentharness/design-patterns
Clone the repo
git clone --depth 1 https://github.com/andr-ca/agentharness

Made for: Cursor.

Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,093 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.01093
Opus 5 $0.00022 $0.00547
Sonnet 5 $0.00009 $0.00219
Haiku 4.5 $0.00004 $0.00109

Measured yesterday against content hash e106dec830fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.cursor/rules/design-patterns.mdc · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Patterns (GoF Reference)

Patterns solve recurring design problems. Don't introduce a pattern to a problem that doesn't exist yet.

Creational — Object Creation

Factory Method

Create objects without knowing the concrete class.

class NotificationFactory:
    @staticmethod
    def create(channel: str) -> Notification:
        match channel:
            case "email": return EmailNotification()
            case "sms":   return SmsNotification()
            case _: raise ValueError(f"Unknown channel: {channel}")

Use when: the exact type to create is determined at runtime, or varies by environment.

Builder

Construct complex objects step by step, separating construction from representation.

const email = new EmailBuilder()
    .to("[email protected]")
    .subject("Hello")
    .body("World")
    .build();

Use when: constructors would have 4+ parameters, especially optional ones.

Behavioral — Object Communication

Strategy

Define a family of algorithms and make them interchangeable at runtime.

class Sorter:
    def __init__(self, strategy: SortStrategy) -> None:
        self._strategy = strategy

    def sort(self, data: list) -> list:
        return self._strategy.sort(data)

Use when: you have multiple ways to do something and want to switch them. Replace if/elif chains.

Observer (Event / Pub-Sub)

One object notifies many dependents without knowing who they are.

class EventEmitter<T> {
    private listeners = new Set<(event: T) => void>();
    on(fn: (event: T) => void) { this.listeners.add(fn); }
    emit(event: T) { this.listeners.forEach(fn => fn(event)); }
}

Use when: one thing changing should trigger reactions in multiple places, without tight coupling.

Command

Encapsulate a request as an object to support undo, logging, or queuing.

@dataclass
class CreateOrderCommand:
    user_id: str
    items: list[OrderItem]

class CommandHandler:
    def handle(self, cmd: CreateOrderCommand) -> Order: ...

Read the full file on GitHub · 167 lines

Changes

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.

  1. yesterday First seen · 167 lines · 43 tokens per session scan A e106dec830fa

Subscribe to this mod's changes

design-patterns is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,093 once invoked, about $0.0002 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.