What is run-lint-checks?

A command guide for running comprehensive lint checks on an Angular and Vite project. Lint checks automatically look for coding, type, style, and design-system problems.

Use it after code changes or before completion to run the project's full lint command, including TypeScript, color, inline-style, and border checks.

It catches quality and consistency issues before code is considered finished or committed.

run-lint-checks — Skill for Cursor by julianoczkowski

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 julianoczkowski/create-trimble-app --skill run-lint-checks

Clone the repo

git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/julianoczkowski/create-trimble-app/run-lint-checks/github.svg)](https://agentmods.dev/skills/julianoczkowski/create-trimble-app/run-lint-checks)

Your own site

<a href="https://agentmods.dev/skills/julianoczkowski/create-trimble-app/run-lint-checks"><img src="https://agentmods.dev/badge/skills/julianoczkowski/create-trimble-app/run-lint-checks/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/julianoczkowski/create-trimble-app/run-lint-checks"><img src="https://agentmods.dev/badge/skills/julianoczkowski/create-trimble-app/run-lint-checks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,224 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.01224
Opus 5.5	$0.00019	$0.00490
Sonnet 5.5	$0.00009	$0.00245
Haiku 4.5	$0.00005	$0.00122

Measured 2mo ago against content hash 747e27846275, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-lint-checks 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 2mo 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.

templates/angular/.cursor/skills/run-lint-checks/SKILL.md · 170 lines

How it starts

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

Run Lint Checks

Automatically run all linting and quality checks for the Angular + Vite project to ensure design system compliance, type safety, and code quality.

When to Use

Before completing any task - Always run lint checks before marking tasks as complete
After making code changes - Run checks after modifying TypeScript, HTML, CSS, or SCSS files
Before committing code - Ensure all quality gates pass before committing
When user requests - Run checks when explicitly requested by the user
During code review - Verify code quality and design system compliance

Instructions

Mandatory Pre-Completion Checklist

CRITICAL: Before marking any development task as complete, you MUST:

Run all lint checks using npm run lint:all
Fix any violations found
Verify TypeScript type checking passes
Ensure all design system compliance checks pass

Running Lint Checks

Execute the comprehensive lint check command:

npm run lint:all

This command runs all checks in sequence:

TypeScript type checking (npm run type-check)
Color compliance (npm run lint:colors)
Inline styles validation (npm run lint:styles)
Border violations (npm run lint:borders)
Opacity utilities (npm run lint:opacity)
Icon usage (npm run lint:icons)
Icon name validation (npm run lint:icon-names)

Individual Lint Commands

If you need to run checks individually:

# TypeScript type checking
npm run type-check

# Design system color compliance
npm run lint:colors

# Inline styles validation
npm run lint:styles

# Border pattern violations
npm run lint:borders

# Opacity utilities validation
npm run lint:opacity

# Modus icons library validation
npm run lint:icons

# Icon name validation
npm run lint:icon-names

Handling Violations

When violations are found:

Read the error messages carefully - Each lint script provides specific file locations and violation details
Fix violations immediately - Don't proceed until all violations are resolved
Re-run checks - After fixing, run npm run lint:all again to verify
Document fixes - If a fix requires architectural changes, explain the reasoning

Read the full file on GitHub · 170 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.

2mo ago First seen · 170 lines · 47 tokens per session scan A 747e27846275

Subscribe to this mod's changes

run-lint-checks is a skill published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,224 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-08-31.

cli modus trimble

run-lint-checks next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
run-lint-checksjulianoczkowski/create-trimble-app	Skill	3	4mo ago	MIT	A	47	Cursor
feishuHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	33	Claude Code, Codex
interviewHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	40	Claude Code, Codex
atmos-configcloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	31	Claude Code
gamedev-shadersericrisco/rsc-harness	Skill	503	2d ago	MIT	A	102	Claude Code, Codex
uniflyhyperb1iss/unifly	Skill	275	6d ago	Apache-2.0	A	63	Claude Code
gap-to-topicWenyuChiou/research-hub	Skill	67	yesterday	MIT	A	188	Claude Code