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/goranerhartic/cursor-development-rules/powertools-parametersgit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWhat 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.00036 | $0.00770 |
| Opus 5 | $0.00018 | $0.00385 |
| Sonnet 5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
powertools-parameters 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Powertools Parameters
Overview
@aws-lambda-powertools/parameters provides a single API for SSM Parameter Store, Secrets Manager, and AppConfig with built-in caching. Use it instead of manual SDK calls and cache Maps. Reduces latency and cost across invocations.
Dependencies
pnpm add @aws-lambda-powertools/parameters
Secrets Manager
// src/shared/secrets/index.ts
import { getSecret } from "@aws-lambda-powertools/parameters/secrets";
import { logger } from "@/shared/logger";
const CACHE_TTL_SECONDS = 300; // 5 minutes
export async function getDatabaseCredentials(): Promise<{
username: string;
password: string;
host: string;
port: number;
database: string;
}> {
const secretId = process.env.DATABASE_SECRET_ARN!;
try {
const value = await getSecret(secretId, {
maxAge: CACHE_TTL_SECONDS,
transform: "json",
});
return value as {
username: string;
password: string;
host: string;
port: number;
database: string;
};
} catch (error) {
logger.error({ err: error, secretId }, "Failed to retrieve secret");
throw error;
}
}
SSM Parameter Store
import { getParameter } from "@aws-lambda-powertools/parameters/ssm";
const opensearchEndpoint = await getParameter("/real-estate/opensearch-endpoint", {
maxAge: 60,
});
const configJson = await getParameter("/real-estate/config", {
maxAge: 120,
transform: "json",
});
AppConfig (Feature Flags / Config)
import { getAppConfig } from "@aws-lambda-powertools/parameters/appconfig";
const config = await getAppConfig("my-app", "my-env", "my-config", {
maxAge: 60,
});
Caching Behavior
- maxAge: Cache TTL in seconds. Same secret/parameter within the same Lambda instance returns cached value.
- Cache is per-instance; cold starts fetch fresh.
- Use shorter maxAge for frequently changing config; longer for secrets.
IAM and CDK
Grant the Lambda role access to the secret or parameter:
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 · 117 lines · 36 tokens per session scan A 46b8efeb3820
powertools-parameters is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 770 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.
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.
netlify-frameworks-nextjs
Next.js on Netlify. Reference for the netlify-frameworks skill.
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.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.