write-lint-rules

write-lint-rules is a skill for Claude Code from mendixlabs/mxcli. It costs 44 tokens per session (10,211 once invoked), scanned A, original, Apache-2.0.

A guide to writing custom Starlark rules, which are small checks that enforce a project's coding conventions during linting.

In plain words
What is it for?
Use it to create rules for naming, quality, design, or security requirements in a Mendix project.
Why use it?
It lets a team catch project-specific problems automatically alongside the built-in lint checks.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to create rules for naming, quality, design, or security requirements in a Mendix project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mendixlabs/mxcli/write-lint-rules
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.

Any agent
npx skills add mendixlabs/mxcli --skill write-lint-rules
Clone the repo
git clone --depth 1 https://github.com/mendixlabs/mxcli

Made for: Claude Code.

Wrote 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.

agentmods badge for write-lint-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/mendixlabs/mxcli/write-lint-rules/github.svg)](https://agentmods.dev/skills/mendixlabs/mxcli/write-lint-rules)
Your own site
<a href="https://agentmods.dev/skills/mendixlabs/mxcli/write-lint-rules"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/write-lint-rules/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-lint-rules

Your own site · 80×15
<a href="https://agentmods.dev/skills/mendixlabs/mxcli/write-lint-rules"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/write-lint-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00044 $0.10211
Opus 5.5 $0.00018 $0.04084
Sonnet 5.5 $0.00009 $0.02042
Haiku 4.5 $0.00004 $0.01021

Measured 4d ago against content hash d85bd95e6049, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-lint-rules 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 4d 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.

.claude/skills/mendix/write-lint-rules/SKILL.md · 711 lines

How it starts

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

Find it fast

sed -n '<from>,<to>p' SKILL.md one section rather than reading the file; ./mxcli syntax <topic> answers how do I write this for a fraction of either.

lines section
25-67 Rule File Structure
68-161 Available Query Functions
162-600 Object Properties
601-613 Helper Functions
614-700 Common Patterns
701-710 Validation

Writing Custom Starlark Lint Rules

Custom lint rules are written in Starlark (a Python-like language) and placed in .claude/lint-rules/ as .star files. They run alongside the built-in rules when mxcli lint -p app.mpr is executed.

Rule File Structure

Every .star file must define metadata constants and a check() function:

RULE_ID = "CUSTOM001"          # unique identifier
RULE_NAME = "MyRule"           # Short display name
DESCRIPTION = "What it checks" # One-line description
CATEGORY = "security"          # Category: naming, quality, design, security, etc.
SEVERITY = "warning"           # hint, info, warning, error

def check():
    violations = []
    # ... iterate data, find issues, append violations ...
    return violations

Catalog data requirements (widgets, refs_to, cycles, …)

Some builtins need a deeper catalog than the default fast build:

  • refs_to, refs_from, widgets, xpath_expressions, activities_for, permissions, permissions_for, strings and the widget_count field of a page or snippet need REFRESH CATALOG FULL — the refs, widgets, xpath_expressions, activities, permissions and strings tables and the widget counts are only written by a full build.
  • The graph-analysis builtins (cycles, module_dependencies, community_of, layer_of, centrality, god_nodes, integration_surface) need REFRESH CATALOG COMMUNITIES (the graph_* tables).

You don't have to do anything: mxcli lint (and the LINT statement) auto-detect these builtins (a call name() and .widget_count in your rule's source and build the catalog at the required depth automatically. If the scan cannot see it — e.g. getattr(p, "widget_count"), or a builtin passed around by name — or you want to be explicit, declare it:

Read the full file on GitHub · 711 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago Changed · +15 lines d85bd95e6049
  2. 7d ago Changed · +12 lines 3a0ea57521ab
  3. 12d ago Changed · +25 lines dfedba1e29ea
  4. 15d ago Changed b69c4a6b2604
  5. 19d ago Changed · +95 lines 1352f85ab5de
  6. 20d ago Changed · +3 lines 58a5b94d1f78
  7. 22d ago Changed 55e8e062142d
  8. 23d ago Changed · +32 lines 6601cad7b4b0
  9. 27d ago Changed · +27 lines 4a58833a10f8
  10. 1mo ago First seen · 502 lines · 44 tokens per session scan A 5a7863cde32b

Subscribe to this mod's changes

write-lint-rules is a skill published in the GitHub repository mendixlabs/mxcli (130 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 10,211 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

codegraph

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…

QwenLM/qwen-code · 0 tokens

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

structured-debugging

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…

QwenLM/qwen-code · 85 tokens

memory-leak-debug

Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.

QwenLM/qwen-code · 42 tokens

bugfix

Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.

QwenLM/qwen-code · 53 tokens

test-failure-explorer

Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.

QwenLM/qwen-code · 32 tokens