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.
npx agentmods add rules/bravew/trove/trove-lambdagit clone --depth 1 https://github.com/bravew/troveWhat 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 | $0.00000 | $0.00625 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
trove-lambda 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
AWS Lambda Conventions
Handler Structure
from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities.typing import LambdaContext
logger = Logger()
@logger.inject_lambda_context(log_event=True)
def handler(event: dict, context: LambdaContext) -> dict:
records = parse_event(event)
for record in records:
process_record(record)
return {"statusCode": 200}
SQS/SNS Event Parsing
def parse_sqs_event(event: dict) -> list[dict]:
return [json.loads(record["body"]) for record in event["Records"]]
def parse_sns_via_sqs(event: dict) -> list[dict]:
messages = []
for record in event["Records"]:
body = json.loads(record["body"])
message = json.loads(body["Message"])
messages.append(message)
return messages
Logging
Follow the same logging rules as trove-python, plus:
- Use
@logger.inject_lambda_context(log_event=True)on handlers - Use
logger.append_keys()for request-scoped context - Use
logger.exception()in error handlers (captures stack trace for Sentry)
IPC Pattern (Backend Communication)
async def call_backend(endpoint: str, payload: dict) -> dict:
async with httpx.AsyncClient() as client:
response = await client.post(
f"{BACKEND_URL}/api/ipc/{endpoint}",
json=payload,
headers={"Authorization": f"Bearer {IPC_TOKEN}"},
timeout=30.0,
)
response.raise_for_status()
return response.json()
CDK Patterns
- One construct per Lambda function
- Use
PythonFunctionfrom@aws-cdk/aws-lambda-python-alpha - Environment variables via CDK
environmentprop, secrets via Secrets Manager - Set
memorySize,timeout, andreservedConcurrentExecutions
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.
- 2d ago First seen · 83 lines · 625 tokens per session scan A 28bb6b715acd
trove-lambda is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 tokens. 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-31.
Other cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
redteam-compute
Compute security sub-agent for an Azure red team engagement. Covers VMs, VMSS, App Service, and Functions. Finds disk encryption gaps, exposed managed identities, plaintext secrets, runCommand exposure, FTP/remote-debug, and missing auth. Containers and Kubernetes (AKS, ACR, Container Apps/Instances) are owned by the…
cloud-workload-cost-estimator
Pre-deployment cost modeling for new workloads, architecture alternatives, and migration plans. Produces estimates the FinOps and Engineering teams both trust, with explicit assumptions and sensitivity ranges.
union-mcp-v2
Rules for using the Union MCP v2 server to run compute- or io-intensive workloads on Flyte.
tanaakk-multi-cloud-iam
クラウド非依存のマルチクラウド IAM 標準(Alibaba/AWS/GCP/Azure に依存しない).
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.