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/thrashr888/terraform-mcp-server/cursorrulesgit clone --depth 1 https://github.com/thrashr888/terraform-mcp-serverWrote 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/thrashr888/terraform-mcp-server/cursorrules)<a href="https://agentmods.dev/rules/thrashr888/terraform-mcp-server/cursorrules"><img src="https://agentmods.dev/badge/rules/thrashr888/terraform-mcp-server/cursorrules.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 | $0.00253 | $0.00253 |
| Opus 5 | $0.00127 | $0.00127 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
cursorrules 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 5d 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
development
- run
npm run buildto build the project - the server needs manually restarted after building
- run
npm run testto run the tests - run
npm run lint:fixto run the linting - run
./test.shto run the tests - run
./test-simple.shto run the tests - locally managed MCP config is in
./.cursor/mcp.jsonand~/Library/Application Support/Claude/claude_desktop_config.json ./api-use.mdhas examples of how to use the API- nodejs version is specified in
.nvmrc - if you're trying something out and it's not working, don't leave the code in the file. delete it.
- don't upgrade dependencies unless it fixes an issue
release
- tests should be passing before releasing
- update the version in
./config.tsand./package.json - update the
./CHANGELOG.mdto reflect customer-facing changes. be concise. - commit, tag, and push to GitHub
- after the CI pipeline completes, create a new release on GitHub using
gh - npm and docker releases are handled automatically via GitHub Actions
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.
- 5d ago First seen · 20 lines · 253 tokens per session scan A 3d48726d3239
cursorrules is a cursor rule published in the GitHub repository thrashr888/terraform-mcp-server (120 stars, last pushed 1y ago), licensed MIT. It adds 253 tokens to every session, about $0.0013 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.