rust-type-system

A set of rules for writing Rust code involving its type system and generics. Rust's type system checks many programming mistakes before the program runs, while generics let code work with different data types.

In plain words
What is it for?
Use it when working on Rust types or generic code. Beyond that, the available information does not say which concrete tasks it covers.
Why use it?
It gives an agent guidance for handling Rust's type-related code consistently. The provided description does not specify the individual rules.

Cursor rule for Cursor

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/ghuntley/groundhog/rust-type-system
Clone the repo
git clone --depth 1 https://github.com/ghuntley/groundhog

Made for: Cursor.

Per session 799 This file is loaded in full into every session.
When invoked 799 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00799 $0.00799
Opus 5 $0.00400 $0.00400
Sonnet 5 $0.00160 $0.00160
Haiku 4.5 $0.00080 $0.00080

Measured yesterday against content hash f4d32e23a4d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rust-type-system 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 yesterday.

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/rules/rust-type-system.mdc · 130 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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.

  1. yesterday First seen · 130 lines · 799 tokens per session scan A f4d32e23a4d5

Subscribe to this mod's changes

rust-type-system is a cursor rule published in the GitHub repository ghuntley/groundhog (402 stars, last pushed 1y ago), licensed AGPL-3.0. It adds 799 tokens to every session, about $0.0040 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.