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/dynamodb-streams)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/dynamodb-streams"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/dynamodb-streams/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/dynamodb-streams"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/dynamodb-streams.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.00027 | $0.00672 |
| Opus 5.5 | $0.00011 | $0.00269 |
| Sonnet 5.5 | $0.00005 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
dynamodb-streams 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DynamoDB Streams
Use DynamoDB Streams for event-driven processing (e.g. syncing to OpenSearch, analytics, cache invalidation). Enable streams on the table in CDK and add a Lambda event source mapping.
Stream Handler for OpenSearch Sync
// src/functions/sync-to-opensearch/handler.ts
import type { DynamoDBStreamHandler, DynamoDBRecord } from "aws-lambda";
import { unmarshall } from "@aws-sdk/util-dynamodb";
import type { AttributeValue } from "@aws-sdk/client-dynamodb";
import { logger } from "@/shared/logger";
import { opensearchClient } from "@/shared/clients/opensearch";
export const handler: DynamoDBStreamHandler = async (event) => {
const bulkOperations: object[] = [];
for (const record of event.Records) {
const operation = processRecord(record);
if (operation) {
bulkOperations.push(...operation);
}
}
if (bulkOperations.length > 0) {
await opensearchClient.bulk({ body: bulkOperations });
logger.info({ operationCount: bulkOperations.length / 2 }, "Bulk indexed to OpenSearch");
}
};
function processRecord(record: DynamoDBRecord): object[] | null {
const eventName = record.eventName;
const newImage = record.dynamodb?.NewImage;
const oldImage = record.dynamodb?.OldImage;
if (!newImage && !oldImage) {
return null;
}
const item = newImage
? unmarshall(newImage as Record<string, AttributeValue>)
: unmarshall(oldImage as Record<string, AttributeValue>);
if (item.entityType !== "Listing") {
return null;
}
const documentId = `${item.propertyId}-${item.listingId}`;
switch (eventName) {
case "INSERT":
case "MODIFY":
return [
{ index: { _index: "listings", _id: documentId } },
{
propertyId: item.propertyId,
listingId: item.listingId,
agentId: item.agentId,
price: item.price,
listingType: item.listingType,
status: item.status,
description: item.description,
photos: item.photos,
createdAt: item.createdAt,
updatedAt: item.updatedAt,
},
];
case "REMOVE":
return [
{ delete: { _index: "listings", _id: documentId } },
];
default:
return null;
}
}
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 · 93 lines · 27 tokens per session scan A f8298de85171
dynamodb-streams is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 672 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
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
rulesforconvex
description: Convex guidelines globs: alwaysApply: true.
startup-migration-bounded-work
Production djangostartup migrate must be bounded; never run makemigrations in production.
redis_rate_limiting
Complete guide for implementing Redis-based rate limiting with authentication troubleshooting and FastAPI integration.
schema
Scalable and secure schema design patterns for relational databases, NoSQL, and APIs. / TR: İlişkisel veri tabanları, NoSQL ve API'ler için ölçeklenebilir ve güvenli şema tasarım kalıpları.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.