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/golid-ai/golid/deploy-infragit clone --depth 1 https://github.com/golid-ai/golidWrote 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/golid-ai/golid/deploy-infra)<a href="https://agentmods.dev/rules/golid-ai/golid/deploy-infra"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/deploy-infra.svg" alt="Measured on agentmods" 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.00000 | $0.01224 |
| Opus 5 | $0.00000 | $0.00612 |
| Sonnet 5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
deploy-infra scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Health check: `HEALTHCHECK CMD curl -f http://localhost:8080/health || exit 1` How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Change Patterns
Thesis: Every env var follows a full chain: config struct, env file, deploy script, service constructor. Secrets go through Secret Manager, never hardcoded.
High-risk, low-frequency changes. Follow the full chain for every modification.
Adding a New Environment Variable
Two chains depending on whether the value is a secret or plain config.
If it's a SECRET (API key, password, signing key):
backend/internal/config/config.go— add field toConfigstruct +os.Getenv()inLoad()config/.env.local— add with dev/sandbox value (local dev only)config/.env.example— add with placeholder- Create in GCP Secret Manager:
echo -n "value" | gcloud secrets create golid-{name}-{env} --data-file=- --project=PROJECT scripts/deploy.sh— addsecret_existsguard + append tosecretsstring inship_api()- Service constructor in
internal/wire/services.go(BuildServices) — passcfg.NewFieldto the service
If it's plain CONFIG (URL, domain, feature flag):
backend/internal/config/config.go— add field toConfigstruct +os.Getenv()inLoad()config/.env.local— add with dev/sandbox valueconfig/.env.example— add with placeholder (backend vars only)frontend/.env.example— add with placeholder (forVITE_*browser-exposed vars only). Per-environment values (e.g. QA vs prodVITE_API_URL) go inconfig/.env.{qa,prod}and are passed as build args during frontend image build.config/.env.qa— add with QA valueconfig/.env.prod— add with production valuescripts/deploy.sh— add to theenv_varsblock inship_api()(if backend needs it at runtime)- Service constructor in
internal/wire/services.go(BuildServices) — passcfg.NewFieldto the service
// config.go
type Config struct {
// ...
NewAPIKey string
}
// In Load():
NewAPIKey: os.Getenv("NEW_API_KEY"),
Docker Patterns
- Multi-stage builds: build stage (Go compile) → runtime stage (minimal image)
- Never copy
.envfiles into images — env vars injected at runtime - Health check:
HEALTHCHECK CMD curl -f http://localhost:8080/health || exit 1 - Non-root user in production images
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.
- 6d ago First seen · 100 lines · 0 tokens per session scan A f5f96596f2c4
deploy-infra is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,224 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
kubernetes
This guide defines definitive best practices for writing, organizing, and securing Kubernetes manifests and Operators, ensuring maintainable, performant, and reliable cloud-native deployments.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
build-deployment
Build, CMake, and Docker deployment.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
deployment
Rails Deployment with Kamal.