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)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/dynamodb"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/dynamodb/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"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/dynamodb.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.00041 | $0.00517 |
| Opus 5.5 | $0.00016 | $0.00207 |
| Sonnet 5.5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
dynamodb 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.
What it actually says
DynamoDB Patterns
Overview
Use single-table design with overloaded PK/SK and GSIs. Use AWS SDK v3: @aws-sdk/client-dynamodb, @aws-sdk/lib-dynamodb (DocumentClient).
Client
DynamoDBDocumentClient.from(DynamoDBClient); singleton;marshallOptions: { removeUndefinedValues: true }; avoidconvertEmptyValues
Key Design
- PK/SK: Composite keys (e.g.
PROPERTY#<id>,LISTING#<id>); useMETADATAor similar for single-item entity record - GSI: Overload GSI1PK/GSI1SK for access patterns (e.g. by owner, by agent, by status+time); project only needed attributes if desired
- Entity type: Include
entityType(or use PK/SK prefix) for filtering
Operations
- GetItem: By PK + SK
- PutItem: Use conditional expression for optimistic locking:
version = :currentVersion; increment version on update - Query: By PK (required); optional SK condition (begins_with, between, =); filter expression for post-query filter
- BatchGetItem: Up to 100 items; handle
UnprocessedKeysand retry - BatchWriteItem: Put/Delete; handle
UnprocessedItems; do not exceed 25 items per request - Scan: Avoid or limit; use parallel scan only when necessary with segment/totalSegments
Optimistic Locking
- Add
version(number) to entities; on update setConditionExpression: 'version = :v',:v= current; increment in update expression
TTL
- Add
ttlattribute (Unix timestamp); enable TTL on table to desired attribute
Conventions
- Single table per service/domain; consistent key naming; always use condition for overwrite-sensitive writes; propagate correlationId in logs
Anti-Patterns
- Multiple tables for same domain; scan without limit; ignoring UnprocessedKeys/UnprocessedItems; no version for concurrent updates
See also: dynamodb-streams.mdc, idempotency.mdc, ../../patterns/architecture.mdc
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 · 47 lines · 41 tokens per session scan A bee147ccbbc6
dynamodb is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 517 once invoked, about $0.0002 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
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
sync-timedb-archive-janitor-contract
Day-close / cold-path worker contracts for synctimedb (A invariants; B tick coordinator retired).
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ı.