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.
npx agentmods add rules/girijashankarj/cursor-handbook/handler-patternsgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/handler-patterns)<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="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 | $0.00000 | $0.00973 |
| Opus 5 | $0.00000 | $0.00487 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00097 |
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 today.
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 — 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
- Validate Request — Schema validation, type checking, required fields
- Validate Business — Business rule validation, entity state checks
- Pre-Processing — Data transformation, enrichment, defaults
- Operation — Core business logic execution
- Post-Operation — Side effects (events, notifications, cache invalidation)
- Response — Format and return response
- 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);
}
}
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.
- today First seen · 113 lines · 0 tokens per session scan A e20e68392cd0
handler-patterns is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 4d 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.
Other cursor rules, from other repositories
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
new_features
Guidelines for integrating new features into the Task Master CLI.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.