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/goranerhartic/cursor-development-rules/lambda-handlersgit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWhat 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.00041 | $0.01952 |
| Opus 5 | $0.00020 | $0.00976 |
| Sonnet 5 | $0.00008 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
lambda-handlers 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 2d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lambda Handler Patterns
Overview
AWS Lambda functions require specific patterns to handle cold starts, memory constraints, timeouts, and concurrent executions efficiently.
Dependencies
Use Middy v7 and Node.js 22 runtime. Middy v7 has breaking changes from v5 (see upgrade guide).
pnpm add @middy/core@^7 @middy/http-json-body-parser@^7 @middy/http-error-handler@^7 @middy/input-output-logger@^7 @middy/http-cors@^7
pnpm add @aws-lambda-powertools/logger @aws-lambda-powertools/tracer @aws-lambda-powertools/metrics
pnpm add -D @types/aws-lambda esbuild
Base Handler Structure
Simple Handler
// src/functions/get-property/handler.ts
import type { APIGatewayProxyHandler, APIGatewayProxyResult } from "aws-lambda";
import { logger } from "@/shared/logger";
export const handler: APIGatewayProxyHandler = async (event, context) => {
// Disable waiting for event loop to empty (faster cold starts)
context.callbackWaitsForEmptyEventLoop = false;
const propertyId = event.pathParameters?.propertyId;
if (!propertyId) {
return {
statusCode: 400,
body: JSON.stringify({ message: "Property ID is required" }),
};
}
try {
const property = await propertyService.findById(propertyId);
if (!property) {
return {
statusCode: 404,
body: JSON.stringify({ message: "Property not found" }),
};
}
return {
statusCode: 200,
body: JSON.stringify(property),
};
} catch (error) {
logger.error({ err: error, propertyId }, "Failed to get property");
return {
statusCode: 500,
body: JSON.stringify({ message: "Internal server error" }),
};
}
};
Middy Middleware Pattern (Recommended)
Middleware Stack Setup
// src/shared/middleware/index.ts
import middy from "@middy/core";
import httpJsonBodyParser from "@middy/http-json-body-parser";
import httpErrorHandler from "@middy/http-error-handler";
import inputOutputLogger from "@middy/input-output-logger";
import httpCors from "@middy/http-cors";
import { injectLambdaContext } from "@aws-lambda-powertools/logger/middleware";
import { captureLambdaHandler } from "@aws-lambda-powertools/tracer/middleware";
import { logger } from "@/shared/logger";
import { tracer } from "@/shared/tracer";
import { correlationIdMiddleware } from "./correlation-id";
import { validationMiddleware } from "./validation";
export function createHandler<TEvent, TResult>(
handler: (event: TEvent, context: Context) => Promise<TResult>
) {
return middy(handler)
.use(injectLambdaContext(logger, { clearState: true }))
.use(captureLambdaHandler(tracer))
.use(correlationIdMiddleware())
.use(httpCors({ origin: "*", credentials: true })) // Real estate web app: allow frontend origin
.use(inputOutputLogger({
logger: (request) => logger.debug(request),
awsContext: true,
}))
.use(httpJsonBodyParser())
.use(httpErrorHandler({ logger: (error) => logger.error({ err: 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.
- 2d ago First seen · 297 lines · 41 tokens per session scan A ee753980a2f0
lambda-handlers is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,952 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.