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/powertools-batch)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/powertools-batch"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/powertools-batch/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/powertools-batch"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/powertools-batch.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.00032 | $0.01166 |
| Opus 5.5 | $0.00013 | $0.00466 |
| Sonnet 5.5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
powertools-batch 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Powertools Batch Processing
Overview
@aws-lambda-powertools/batch provides a standard way to process SQS, Kinesis, and DynamoDB Streams events with automatic partial batch failure reporting. Use it instead of manually building batchItemFailures and classifying retryable errors.
Dependencies
pnpm add @aws-lambda-powertools/batch
SQS Batch Processor
// src/functions/process-listings/handler.ts
import type { SQSEvent, SQSRecord, SQSBatchResponse } from "aws-lambda";
import { BatchProcessor, EventType, processPartialResponse } from "@aws-lambda-powertools/batch";
import { logger } from "@/shared/logger";
import { listingService } from "@/services/listing.service";
const processor = new BatchProcessor(EventType.SQS);
export const handler = async (event: SQSEvent): Promise<SQSBatchResponse> => {
return processPartialResponse(event, processor, async (record: SQSRecord) => {
const message = JSON.parse(record.body);
const { eventType, payload } = message.data;
logger.info({ eventType, messageId: record.messageId }, "Processing event");
const result = await listingService.handleListingPublished(payload);
if (!result.success) {
if (result.error.isRetryable) {
throw new Error(result.error.message); // Will be reported as batch item failure
}
throw new NonRetryableError(result.error.message, result.error.code);
}
});
};
class NonRetryableError extends Error {
constructor(
message: string,
public readonly code: string
) {
super(message);
this.name = "NonRetryableError";
}
}
Retryable vs Non-Retryable
Powertools Batch reports failed items so SQS retries them. For non-retryable errors (e.g. validation), throw a custom error and use a failure handler to avoid retries, or let the message eventually go to the DLQ after max receives. To skip retries for non-retryable errors, throw with a specific name and handle in a custom onFailure callback (see Powertools docs) or use your existing SQS retry ladder and DLQ.
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 · 129 lines · 32 tokens per session scan A 87aef66f7c9d
powertools-batch is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,166 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
cloudflare-email-telegram-cursorrules-prompt-file
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
implement-graceful-shutdown-for-your-application
Cursor rule "implement-graceful-shutdown-for-your-application" from PaulJPhilp/EffectPatterns, covering implement graceful shutdown for your application and example.
service-bindings
Worker-to-Worker RPC - bindings.worker() by name, WorkerEntrypoint callee, typed RPC deferred, requestId propagation.
hatch3r-scalability
CQ6 Scalability Quality measurement rule — stateless-handler ratio, back-pressure pattern adoption, idempotency-key adoption on POST/PUT/PATCH, queue offloading for >1s ops, pool sizing per concurrency profile.
cloudflare-workers-hono-angular-saas-cursorrules-prompt-file
Cursor rule "cloudflare-workers-hono-angular-saas-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering cloudflare workers + hono + angular saas, stack, typescript, hono api and angular.
knative-istio-typesense-gpu-cursorrules-prompt-fil
description: "Cursor rules for Knative development with Istio, Typesense, and GPU integration." globs: / alwaysApply: false.