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/brighton-labs/railguard-cursor-coding/ml-secure-railguard-availablegit clone --depth 1 https://github.com/brighton-labs/railguard-cursor-codingWrote 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/brighton-labs/railguard-cursor-coding/ml-secure-railguard-available)<a href="https://agentmods.dev/rules/brighton-labs/railguard-cursor-coding/ml-secure-railguard-available"><img src="https://agentmods.dev/badge/rules/brighton-labs/railguard-cursor-coding/ml-secure-railguard-available.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.00752 | $0.00752 |
| Opus 5 | $0.00376 | $0.00376 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
ml-secure-railguard-available 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This rule supports secure-by-default machine learning code generation, covering:
- Model checkpoint handling
- Trusted use of HuggingFace, PyTorch, or scikit-learn
- Inference-time protections
- Logging and resource handling
Note: All input validation, sanitization, schema enforcement, and LLM reasoning scaffolding is provided by:
.cursor/rules/railguard-input-validation.mdc
(Based on the RAILGUARD Framework for secure behavior enforcement across languages)
Model Loading & Deserialization
- Use
torch.load()orpickle.load()only on trusted, versioned, local files. - Avoid deserializing full Python objects unless necessary. Prefer
state_dictloading (e.g.,model.load_state_dict(...)) - If using
from_pretrained(), ensure the model name is official or internally versioned. - When downloading models, validate integrity using checksums if possible.
Data Handling & Preprocessing
- Avoid using raw
eval()orexec()to interpret formulas or hyperparameters. - Prefer explicit schema-based checks for:
- Number of features
- Tensor dimensions
- String encoding assumptions
- Do not transform user input without validating structure first.
For validation and sanitation of CSVs, JSONs, NumPy arrays, and request inputs — refer to .cursor/rules/input-validation.mdc.
Inference Logic & Output Handling
- Do not log input text, tokens, or raw payloads directly (especially for NLP or PII-sensitive data).
- Use
with torch.no_grad():or equivalent when performing inference. - Ensure inference outputs are typed, validated, and never expose model internals (e.g., logits, hidden states) unless required.
File & Resource Access
- Always open files using
with open(...)syntax. - Set read-only access unless modification is required.
- Avoid writing cache or checkpoint data to shared or user-supplied paths.
Logging & Monitoring
- Use Python’s
loggingmodule — notprint(). - Mask or exclude sensitive input/output data in logs.
- Log model version, inference success/failure, and prediction metadata — not raw data.
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 · 103 lines · 752 tokens per session scan A e2c32dc38731
ml-secure-railguard-available is a cursor rule published in the GitHub repository brighton-labs/railguard-cursor-coding (13 stars, last pushed 1y ago), licensed MIT. It adds 752 tokens to every session, about $0.0038 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
llm-layer
LLM provider implementation patterns.
tensorflow
TensorFlow: Keras, model training, production deployment.
cursorrules
Cursor rule "cursorrules" from Clarity-Digital-Twin/brain-go-brrr, covering .cursorrules - brain-go-brrr project (fixed architecture), rule #1: no parallel implementations ever, experiments/trainanything.py - must be thin, rule #2: check before building and rule #3: normalization is critical.
006_Program_of_Thought_Tutorial
DSPY 3 Program of Thought Tutorial - Production code reasoning system from official DSPy 3.0.1 tutorial.
standards-data-eng
Mandatory standards for Python and SQL data pipelines.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.