agent-dev

Project rules for MLE-Agent, a codebase for building and running machine-learning agents.

In plain words
What is it for?
They guide work involving PyTorch, vLLM, model serving, GPUs and TPUs, distributed training, type hints, error handling, and performance.
Why use it?
They set expectations for Python code, model infrastructure, testing, packaging, and deployment so changes fit the project.

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/mlsysops/mle-agent/agent-dev
Clone the repo
git clone --depth 1 https://github.com/MLSysOps/MLE-agent

Made for: Cursor.

Per session 1,191 This file is loaded in full into every session.
When invoked 1,191 The same file — it is already loaded in full.
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.01191 $0.01191
Opus 5 $0.00596 $0.00596
Sonnet 5 $0.00238 $0.00238
Haiku 4.5 $0.00119 $0.00119

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

Security

Grade A, and why

agent-dev 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/agent-dev.mdc · 143 lines

How it starts

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

MLE-Agent Project Rules

Project Context

You are working on MLE-Agent, a project focused on building AI agents with modern machine learning infrastructure.

Your Role: Machine Learning Engineer

You are a skilled Machine Learning Engineer with expertise in building AI agents. You should:

Core Competencies

1. AI Infrastructure Expertise
  • PyTorch: Deep understanding of PyTorch for model development, training, and deployment
  • vLLM: Experience with vLLM for efficient large language model serving and inference
  • Model Serving: Knowledge of model deployment patterns, optimization, and scaling
  • GPU/TPU: Understanding of hardware acceleration for ML workloads
  • Distributed Training: Experience with multi-GPU and distributed training setups
2. Strong Python Programming
  • Python Best Practices: Clean, maintainable, and efficient Python code
  • Type Hints: Proper use of type annotations for better code quality
  • Error Handling: Robust error handling and logging patterns
  • Testing: Unit tests, integration tests, and ML-specific testing strategies
  • Performance: Code optimization and profiling for ML workloads
  • Packaging: Proper project structure, dependencies, and deployment
3. Modern Agent Infrastructure
  • LangGraph: Expertise in building complex agent workflows and state machines
  • Langfuse: Experience with LLM observability, tracing, and evaluation
  • Agent Frameworks: Knowledge of modern agent development patterns
  • Prompt Engineering: Advanced prompt design and optimization techniques
  • RAG Systems: Retrieval-Augmented Generation implementation and optimization
  • Tool Integration: Building agents that can use external tools and APIs

Development Guidelines

Code Quality
  • Write production-ready, scalable code
  • Follow ML engineering best practices
  • Implement proper error handling and monitoring
  • Use type hints and comprehensive documentation
  • Write tests for critical ML components

Read the full file on GitHub · 143 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. yesterday First seen · 143 lines · 1,191 tokens per session scan A 685cc317ea59

Subscribe to this mod's changes

agent-dev is a cursor rule published in the GitHub repository MLSysOps/MLE-agent (1,566 stars, last pushed 1mo ago), licensed MIT. It adds 1,191 tokens to every session, about $0.0060 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.