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 skills add julianoczkowski/create-trimble-app --skill run-lint-checksgit clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWrote 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/skills/julianoczkowski/create-trimble-app/run-lint-checks)<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.
<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>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 | $0.00023 | $0.00612 |
| Sonnet 5 | $0.00009 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
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 10d 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 — 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:allagain to verify - Document fixes - If a fix requires architectural changes, explain the reasoning
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.
- 10d ago First seen · 170 lines · 47 tokens per session scan A 747e27846275
run-lint-checks is a skill published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,224 once invoked, about $0.0002 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.