lint

lint is a skill for Claude Code from Zate/cc-plugins. It costs 72 tokens per session (2,316 once invoked), scanned A, original, MIT.

A checker for Claude Code plugins, skills, and hooks. It examines their files and can also review descriptions and test results.

In plain words
What is it for?
Use it to audit a whole plugin, one skill file, or hooks, and optionally apply high-severity fixes or improve descriptions.
Why use it?
It helps find correctness problems, inefficient instructions, and quality issues before they cause failures or make an add-on harder to use.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions .claude-plugin; names the AskUserQuestion tool.

Part of the plugin-lint plugin — 1 skill shipped together

Good fit Use it to audit a whole plugin, one skill file, or hooks, and optionally apply high-severity fixes or improve descriptions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zate/cc-plugins/lint
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 Zate/cc-plugins --skill lint
Clone the repo
git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Or install plugin-lint, the plugin that ships this one along with the rest of its 1 skill.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/zate/cc-plugins/lint"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,316 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.02316
Opus 5.5 $0.00029 $0.00926
Sonnet 5.5 $0.00014 $0.00463
Haiku 4.5 $0.00007 $0.00232

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

Security

Grade A, and why

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

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.

plugins/plugin-lint/skills/lint/SKILL.md · 274 lines

How it starts

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

plugin-lint

Orchestrated quality audit for Claude Code plugins. Runs static correctness checks first (the unique value), then delegates to existing tools for depth.

Flags:

  • (default): Full lint — static analysis + skill-creator description optimization
  • --static-only: Skip description optimization, faster pass
  • --fix: Auto-apply all HIGH severity fixes without prompting

Phase 1: Discover Target

Parse $ARGUMENTS. Extract path and flags.

Target resolution:

  • No path → use current working directory
  • Path ends in SKILL.md → single skill file
  • Path contains hooks/ or ends in hooks.json → hooks audit only
  • Path contains .claude-plugin/ or has plugin.json → whole plugin
  • Otherwise → try as plugin root, skill dir, or hooks dir in that order

Enumerate components (silent):

find "$TARGET" -name "SKILL.md" 2>/dev/null
find "$TARGET" -name "hooks.json" 2>/dev/null
find "$TARGET" -name "*.sh" -path "*/hooks/*" 2>/dev/null
find "$TARGET" -name "*.md" -path "*/agents/*" 2>/dev/null
find "$TARGET" -name "plugin.json" 2>/dev/null

Store discovered files. Note counts: N skills, M hooks, P agents.


Phase 2: Static Correctness Audit

Read all three reference files before starting:

  • ${CLAUDE_SKILL_DIR}/references/hook-schemas.md
  • ${CLAUDE_SKILL_DIR}/references/frontmatter-fields.md
  • ${CLAUDE_SKILL_DIR}/references/common-mistakes.md

Collect findings as a list. Each finding: {severity, file, line, issue, fix}.

2a. Audit hooks.json files

For each hooks.json found:

if condition syntax:

grep -n '"if"' "$HOOKS_JSON"

Flag any value containing ==, ===, ||, &&, != — these are JS expressions, not permission-rule syntax. Correct form: "Bash", "Bash(git *)", "Write".

hookSpecificOutput event names:

grep -n '"hookEventName"' "$HOOKS_JSON"

Cross-reference against the valid-events table in hook-schemas.md. Flag "PreCompact" — it has no schema entry. Flag any unknown event name.

Read the full file on GitHub · 274 lines

Files

What ships with it

3 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 · 274 lines · 72 tokens per session scan A 910dae7ce010

Subscribe to this mod's changes

lint is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 2,316 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens