python-conventions

A set of Python coding rules for the Dingo software development kit. It covers formatting, type hints, evaluator methods, optional imports, and access to optional data fields.

In plain words
What is it for?
Use it when writing or reviewing Dingo Python code, especially evaluators, data access, imports, and dependency-related features.
Why use it?
It keeps Python changes compatible with the project's checks and avoids failures when optional libraries or fields are missing.

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/migoxlab/dingo/python-conventions
Clone the repo
git clone --depth 1 https://github.com/MigoXLab/dingo

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 579 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.00000 $0.00579
Opus 5 $0.00000 $0.00290
Sonnet 5 $0.00000 $0.00116
Haiku 4.5 $0.00000 $0.00058

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

Security

Grade A, and why

python-conventions 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/python-conventions.mdc · 83 lines

How it starts

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

Python Conventions

Code Style

  • Follow PEP 8 (enforced by pre-commit hooks)
  • Use type hints for function signatures
  • Use @classmethod for evaluator eval() methods
  • Prefer getattr(obj, 'field', default) over direct attribute access for optional Data fields

Import Rules

  • Core deps (numpy, pydantic, requests, etc.): top-level imports OK
  • Optional deps (pyarrow, transformers, boto3, sqlalchemy, cv2, fasttext, etc.): must use lazy imports inside methods with clear ImportError messages:
# Correct — lazy import with helpful error
def load_data(self):
    try:
        import pyarrow.parquet as pq
    except ImportError:
        raise ImportError("pyarrow is required for Parquet support. Install: pip install dingo-python[parquet]")

# Wrong — top-level import of optional dep
import pyarrow.parquet as pq

Evaluator Patterns

Rule Evaluator

@Model.rule_register('QUALITY_BAD_CATEGORY', ['default', 'pretrain'])
class RuleMyCheck(BaseRule):
    _required_fields = [RequiredField.CONTENT]

    @classmethod
    def eval(cls, input_data: Data) -> EvalDetail:
        res = EvalDetail(metric=cls.__name__)
        # evaluation logic
        if problem_found:
            res.status = True
            res.label = [f"{cls.metric_type}.{cls.__name__}"]
            res.reason = ["Description of the issue"]
        else:
            res.label = [QualityLabel.QUALITY_GOOD]
        return res

LLM Evaluator

@Model.llm_register('LLMMyEvaluator')
class LLMMyEvaluator(BaseOpenAI):
    prompt = """Your evaluation prompt here..."""

    @classmethod
    def build_messages(cls, input_data: Data) -> List:
        return [
            {'role': 'system', 'content': cls.prompt},
            {'role': 'user', 'content': input_data.content}
        ]

Error Handling

  • Evaluators should not raise exceptions for bad input data; return EvalDetail with appropriate error label instead
  • Use log.warning() / log.error() from dingo.utils for logging
  • External API calls: always handle timeouts and connection errors

Read the full file on GitHub · 83 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 · 83 lines · 0 tokens per session scan A b10ae97aa121

Subscribe to this mod's changes

python-conventions is a cursor rule published in the GitHub repository MigoXLab/dingo (751 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 579 tokens. 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.