A Cursor rule for writing and checking Terraform configuration, which is used to create and manage cloud and software-service infrastructure. It supplies provider-specific reference details and examples for Terraform resources.

Use it when creating, debugging, importing, or moving Terraform or HCL code, especially when configuring a cloud or SaaS provider. It can also provide recipes for combining resources across providers.

It reduces guesswork about valid resource settings, import formats, deprecated options, and recent provider changes. It also helps prevent made-up Terraform names or arguments.

cursor-rule — Cursor rule by vegastack

Install

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.

agentmods

npx agentmods add rules/vegastack/vegastack-cli/cursor-rule

Clone the repo

git clone --depth 1 https://github.com/vegastack/vegastack-cli

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 577 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.00577
Opus 5	$0.00000	$0.00289
Sonnet 5	$0.00000	$0.00115
Haiku 4.5	$0.00000	$0.00058

Measured 2d ago against content hash 959c24ab8f8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursor-rule 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.

cursor-rule.mdc · 39 lines

What it actually says

vegastack-terraform (Cursor rule)

This rule mirrors the SKILL.md shipped at <plugin-root>/skills/vegastack/SKILL.md. After installing @vegastack/cli, run vegastack skills install --agent cursor to drop this .mdc into <project>/.cursor/rules/.

How to use

Run vegastack tf "<user request>" (one call; the harness auto-detects the provider). Output is one JSON envelope with files[], knowledge[], recipes[], concept_aliases_used[].
Read knowledge[] first — those cards override stale training memory when overrides_training: true.
The top-K files[] arrive enriched with manifest_entry (top-level args, blocks: {}, import_syntax, deprecated, recommended_companions) and the inline example_usage block. No follow-up jq or grep needed for ~95% of tasks.
Cite citations[] (file paths + knowledge-card IDs + recipe IDs) in your reply.

Hard rules

Never invent resource names or arguments. The manifest is the source of truth.
Never fabricate import IDs. Use manifest_entry.import_syntax.command verbatim.
Respect deprecated: true — tell the user before generating code.
One provider per vegastack tf call. Multi-provider work uses recipes[].
Never write to ~/.config/vegastack/bundle/ from a tool call — the bundle is read-only.

Full reference

For the complete workflow, examples, and reference files, read <plugin-root>/skills/vegastack/SKILL.md and the files in <plugin-root>/skills/vegastack/references/.

Changes

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 · 39 lines · 0 tokens per session scan A 959c24ab8f8c

Subscribe to this mod's changes

cursor-rule is a cursor rule published in the GitHub repository vegastack/vegastack-cli (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 577 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.

Cloud DevOps and cloud

aws-ecs

Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.

sanjeed5/awesome-cursor-rules-mdc · 2,640 tokens

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…

Contoso-State/red-team-agent-orchestration · 85 tokens

cursor-rule

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

vegastack-terraform (Cursor rule)

How to use

Hard rules

Full reference

What this file has done since we first saw it

Other cursor rules, from other repositories

aws-ecs

redteam-compute

cloud-workload-cost-estimator

union-mcp-v2

tanaakk-multi-cloud-iam

angular-20