chatcli: Skill for Claude Code

.agent/skills/lint-and-validate/SKILL.md

lint-and-validate is a skill for Claude Code from diillson/chatcli. It costs 0 tokens per session (450 once invoked), scanned A, a copy of lint-and-validate, Apache-2.0.

A set of procedures for checking code quality after changes. Linting finds style and common code problems, while static analysis checks code without running it.

In plain words
What is it for?
Use it after code changes in Node.js, TypeScript, or Python projects to run linters, type checks, and security checks.
Why use it?
It catches syntax, type, style, and some security problems before work is finished. It also defines a repeatable loop for fixing failures and checking again.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is diillson/chatcli's own configuration. It tells Claude Code how to work on chatcli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything chatcli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to diillson/chatcli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/diillson/chatcli/main/.agent/skills/lint-and-validate/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/diillson/chatcli

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 lint-and-validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/diillson/chatcli/lint-and-validate/github.svg)](https://agentmods.dev/skills/diillson/chatcli/lint-and-validate)
Your own site
<a href="https://agentmods.dev/skills/diillson/chatcli/lint-and-validate"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/lint-and-validate/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 lint-and-validate

Your own site · 80×15
<a href="https://agentmods.dev/skills/diillson/chatcli/lint-and-validate"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/lint-and-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 450 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 84% copy Near-identical to another mod 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.00000 $0.00450
Opus 5.5 $0.00000 $0.00180
Sonnet 5.5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

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

Security

Grade A, and why

lint-and-validate 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/lint_runner.py, scripts/type_coverage.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

84% identical to lint-and-validate — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agent/skills/lint-and-validate/SKILL.md · 46 lines

What it actually says

Lint and Validate Skill

MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

Procedures by Ecosystem

Node.js / TypeScript
  1. Lint/Fix: npm run lint or npx eslint "path" --fix
  2. Types: npx tsc --noEmit
  3. Security: npm audit --audit-level=high
Python
  1. Linter (Ruff): ruff check "path" --fix (Fast & Modern)
  2. Security (Bandit): bandit -r "path" -ll
  3. Types (MyPy): mypy "path"

The Quality Loop

  1. Write/Edit Code
  2. Run Audit: npm run lint && npx tsc --noEmit
  3. Analyze Report: Check the "FINAL AUDIT REPORT" section.
  4. Fix & Repeat: Submitting code with "FINAL AUDIT" failures is NOT allowed.

Error Handling

  • If lint fails: Fix the style or syntax issues immediately.
  • If tsc fails: Correct type mismatches before proceeding.
  • If no tool is configured: Check the project root for .eslintrc, tsconfig.json, pyproject.toml and suggest creating one.

Strict Rule: No code should be committed or reported as "done" without passing these checks.


Scripts

Script Purpose Command
scripts/lint_runner.py Unified lint check python scripts/lint_runner.py <project_path>
scripts/type_coverage.py Type coverage analysis python scripts/type_coverage.py <project_path>
Files

What ships with it

2 files 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. 1mo ago First seen · 46 lines · 0 tokens per session scan A 00497ead822b

Subscribe to this mod's changes

lint-and-validate is a skill published in the GitHub repository diillson/chatcli (93 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 450 tokens. A static security scan graded it A with 0 findings. It is 84% identical to lint-and-validate, differing in 4 lines, and is treated as a copy.

Related

Other skills, from other repositories

error-recovery

A guide to detecting and recovering from failures in long-running AI agents. It covers API outages, bad tool calls, broken conversation state, stalled streams, repeated loops, retries, fallback models, and circuit breakers that stop repeated failure.

bojieli/ai-agent-book · 111 tokens

coding-agent-harness

A guide to building the surrounding system that lets an AI agent safely work on code. This system provides tools, rules, tests, feedback, permissions, and ways to undo changes.

bojieli/ai-agent-book · 106 tokens

04-audit

Audit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.

ai-driven-dev/framework · 54 tokens

07-refactor

Improve code across four axes (cleanup, performance, security, architecture) by scanning and fixing, or applying a pushed audit report. Use when the user wants to refactor, optimize, harden, or remove code. Not for read-only diagnosis or adding tests.

ai-driven-dev/framework · 57 tokens

03-assert

Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.

ai-driven-dev/framework · 39 tokens

08-debug

Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.

ai-driven-dev/framework · 52 tokens