rust-types

A Rust code-review command for replacing vague primitive values with types that express their meaning. Rust is a programming language, and a newtype is a small custom type used to distinguish values such as user IDs, order IDs, or email addresses.

In plain words
What is it for?
Use it to find strings, numbers, and booleans that represent domain concepts, then model them as validated types or descriptive enums.
Why use it?
It moves validation and state rules into the type system, reducing confusion between similar values and making invalid combinations harder to represent.

Command

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 commands/mathisk2095/jko-claude-plugins/rust-types
Clone the repo
git clone --depth 1 https://github.com/mathisk2095/jko-claude-plugins
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 761 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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00761
Opus 5 $0.00017 $0.00380
Sonnet 5 $0.00007 $0.00152
Haiku 4.5 $0.00003 $0.00076

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

Security

Grade A, and why

rust-types 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.

plugins/rust/commands/rust-types.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rust Types — Strengthen the Domain Model

Push runtime checks into the type system. Every runtime assert!, if !valid, or "this should never happen" comment is a type waiting to be born.

Preparation

  1. Read the target code and identify the domain concepts.
  2. Look for primitive types carrying domain meaning (String for emails, u64 for IDs, bool for states).

Strengthening Steps

Step 1: Find Primitive Obsession

Run in the shell:

rg --type rust 'fn \w+\(.*: (String|&str|u32|u64|i32|i64|bool|f64)' src/ -n | head -30

For each function taking raw primitives that represent domain concepts:

  • String for an email → struct Email(String) with validation in constructor
  • u64 for an ID → struct UserId(u64), struct OrderId(u64) (distinct types!)
  • f64 for money → struct Currency { amount: i64, code: CurrencyCode } (never float for money)

Step 2: Replace Booleans with Enums

Run in the shell:

rg --type rust 'fn \w+\(.*: bool' src/ -n

For each boolean parameter:

// Before: process(data, true, false)  — what do these mean?
// After:
enum Direction { Forward, Backward }
enum OutputMode { Raw, Formatted }
fn process(data: &Data, dir: Direction, mode: OutputMode)

Step 3: Make Illegal States Unrepresentable

Look for:

  • Structs with fields that can be in inconsistent states → use an enum
  • Option<A> + Option<B> where exactly one must be Some → use an enum
  • State transitions modeled with mutable fields → use the typestate pattern
// Before: can be in invalid state (title set but no body)
struct Post { title: Option<String>, body: Option<String>, published: bool }

// After: invalid states are compile errors
enum Post {
    Draft { title: String },
    Review { title: String, body: String },
    Published { title: String, body: String, url: Url },
}

Step 4: Validated Constructors

For every newtype, ensure construction goes through validation:

pub struct Email(String);

impl Email {
    pub fn new(s: impl Into<String>) -> Result<Self, ValidationError> {
        let s = s.into();
        if !s.contains('@') { return Err(ValidationError::InvalidEmail); }
        Ok(Self(s))
    }
}

Read the full file on GitHub · 96 lines

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. 2d ago First seen · 96 lines · 35 tokens per session scan A 509873b1dbbf

Subscribe to this mod's changes

rust-types is a command published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 761 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-31.