handler-patterns

handler-patterns is a cursor rule for Cursor from girijashankarj/cursor-handbook. It costs 0 tokens per session (973 once invoked), scanned A, original, MIT.

A set of rules for organizing API handlers, the code that receives requests and returns responses, into consistent validation, processing, operation, and cleanup steps.

In plain words
What is it for?
Use it when creating or editing API routes and handlers, including request schemas, business validation, data transformation, core operations, and response formatting.
Why use it?
It makes request handling easier to follow and helps ensure validation, business checks, side effects, and responses are not accidentally skipped.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when creating or editing API routes and handlers, including request schemas, business validation, data transformation, core operations, and response formatting.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/girijashankarj/cursor-handbook/handler-patterns
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.

Clone the repo
git clone --depth 1 https://github.com/girijashankarj/cursor-handbook

Made for: Cursor.

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

agentmods badge for handler-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/handler-patterns/github.svg)](https://agentmods.dev/rules/girijashankarj/cursor-handbook/handler-patterns)
Your own site
<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/handler-patterns"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/handler-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.

agentmods 80×15 button for handler-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/handler-patterns"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/handler-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 973 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00973
Opus 5.5 $0.00000 $0.00389
Sonnet 5.5 $0.00000 $0.00195
Haiku 4.5 $0.00000 $0.00097

Measured 1mo ago against content hash e20e68392cd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.cursor/rules/backend/handler-patterns.mdc · 113 lines

How it starts

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

Handler Pattern Rules

Handler Flow

Every API handler MUST follow this {{CONFIG.patterns.handlerFlowSteps}}-step flow:

Step-by-Step Flow

  1. Validate Request — Schema validation, type checking, required fields
  2. Validate Business — Business rule validation, entity state checks
  3. Pre-Processing — Data transformation, enrichment, defaults
  4. Operation — Core business logic execution
  5. Post-Operation — Side effects (events, notifications, cache invalidation)
  6. Response — Format and return response
  7. Exit — Cleanup, logging

Handler Directory Structure

{{CONFIG.paths.handlerBasePath}}/{entity}/{operation}/
├── {{CONFIG.fileNames.handlerEntry}}        # Handler entry point
├── {{CONFIG.folderNames.logic}}/
│   ├── validate-request.ts                   # Step 1
│   ├── validate-business.ts                  # Step 2
│   ├── pre-processing.ts                     # Step 3
│   ├── operation.ts                          # Step 4
│   ├── post-operation.ts                     # Step 5
│   └── response.ts                           # Step 6
└── {{CONFIG.folderNames.schemas}}/
    ├── {{CONFIG.fileNames.requestSchema}}    # Request validation schema
    └── {{CONFIG.fileNames.responseSchema}}   # Response format schema

Handler Entry Point Template

import { Request, Response, NextFunction } from '{{CONFIG.techStack.framework}}';
import { validateRequest } from './logic/validate-request';
import { validateBusiness } from './logic/validate-business';
import { preProcessing } from './logic/pre-processing';
import { operation } from './logic/operation';
import { postOperation } from './logic/post-operation';
import { formatResponse } from './logic/response';
import { logger } from '{{CONFIG.paths.commonPath}}/logger';

export async function handler(req: Request, res: Response, next: NextFunction) {
  const correlationId = req.headers['x-correlation-id'] as string;
  const log = logger.child({ correlationId, operation: 'handler-name' });

  try {
    // Step 1: Validate Request
    const validatedInput = await validateRequest(req.body);

    // Step 2: Validate Business Rules
    await validateBusiness(validatedInput);

    // Step 3: Pre-Processing
    const processedData = await preProcessing(validatedInput);

    // Step 4: Core Operation
    const result = await operation(processedData);

    // Step 5: Post-Operation (async side effects)
    await postOperation(result);

    // Step 6: Response
    const response = formatResponse(result);

    // Step 7: Exit
    log.info({ status: 'success' }, 'Handler completed');
    return res.status(200).json(response);
  } catch (error) {
    log.error({ error: error.message }, 'Handler failed');
    next(error);
  }
}

Read the full file on GitHub · 113 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. 1mo ago First seen · 113 lines · 0 tokens per session scan A e20e68392cd0

Subscribe to this mod's changes

handler-patterns is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 973 tokens. 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-09-03.