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/GoranErhartic/cursor-development-rulesWrote 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/goranerhartic/cursor-development-rules/logging-setup)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/logging-setup"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/logging-setup/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/goranerhartic/cursor-development-rules/logging-setup"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/logging-setup.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.00024 | $0.01624 |
| Opus 5.5 | $0.00010 | $0.00650 |
| Sonnet 5.5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
logging-setup 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lambda Logger Setup & Best Practices
Overview
Lambda observability requires structured logging, distributed tracing, and metrics. AWS Lambda Powertools provides a unified approach for TypeScript. Powertools 2.31+ adds event handler tracer middleware for HTTP routes and improved Parameters error handling.
Dependencies
pnpm add @aws-lambda-powertools/logger @aws-lambda-powertools/tracer @aws-lambda-powertools/metrics
Logger Setup
Configuration
// src/shared/logger/index.ts
import { Logger } from "@aws-lambda-powertools/logger";
export const logger = new Logger({
serviceName: process.env.SERVICE_NAME ?? "real-estate-api",
logLevel: (process.env.LOG_LEVEL as "DEBUG" | "INFO" | "WARN" | "ERROR") ?? "INFO",
persistentLogAttributes: {
environment: process.env.ENVIRONMENT ?? "development",
version: process.env.VERSION ?? "unknown",
// Multi-tenant real estate: set tenantId per request via logger.appendKeys({ tenantId })
...(process.env.TENANT_ID && { tenantId: process.env.TENANT_ID }),
},
});
// Re-export for convenience
export type { Logger } from "@aws-lambda-powertools/logger";
Usage in Handlers
// src/functions/create-listing/handler.ts
import type { APIGatewayProxyHandler } from "aws-lambda";
import { logger } from "@/shared/logger";
export const handler: APIGatewayProxyHandler = async (event, context) => {
// Add Lambda context to all logs
logger.addContext(context);
// Add request-specific context (tenantId from auth for multi-tenant real estate)
logger.appendKeys({
correlationId: event.headers["x-correlation-id"],
path: event.path,
method: event.httpMethod,
...(event.requestContext?.authorizer?.claims?.sub && {
tenantId: event.requestContext.authorizer.claims["custom:tenantId"],
}),
});
logger.info("Processing create listing request");
try {
const body = JSON.parse(event.body ?? "{}");
logger.debug({ body }, "Request body parsed");
const result = await listingService.create(body);
if (!result.success) {
logger.warn({ error: result.error }, "Listing creation failed");
return { statusCode: 400, body: JSON.stringify(result.error) };
}
logger.info({ listingId: result.data.id }, "Listing created successfully");
return { statusCode: 201, body: JSON.stringify(result.data) };
} catch (error) {
logger.error({ err: error }, "Unexpected error in create listing handler");
throw 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.
- 1mo ago First seen · 223 lines · 24 tokens per session scan A 9da6962ddda5
logging-setup is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 1,624 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.