powertools-batch

Guidelines for processing batches of messages or events with AWS Lambda using AWS Powertools. Powertools is a toolkit that reports which records failed in SQS, Kinesis, or DynamoDB Streams batches.

In plain words
What is it for?
Building record-by-record processors, handling partial failures, and returning the required failed-message information for SQS, Kinesis, and DynamoDB Streams.
Why use it?
They prevent successful records from being retried just because another record in the same batch failed, while still allowing failed records to be retried.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/goranerhartic/cursor-development-rules/powertools-batch
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,166 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00032 $0.01166
Opus 5 $0.00016 $0.00583
Sonnet 5 $0.00006 $0.00233
Haiku 4.5 $0.00003 $0.00117

Measured 2d ago against content hash 87aef66f7c9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

.cursor/rules/languages/aws-lambda/powertools-batch.mdc · 129 lines

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.

Read the full file on GitHub · 129 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. 2d ago First seen · 129 lines · 32 tokens per session scan A 87aef66f7c9d

Subscribe to this mod's changes

powertools-batch is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,166 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.