lint

lint is a command for Claude Code from RaNDoM6913/claude-code-superkit. It costs 21 tokens per session (2,063 once invoked), scanned A, original, MIT.

A command that detects the project's supported formatters and linters, then runs them in the correct order. A formatter automatically adjusts code style; a linter checks code for style and common problems.

In plain words
What is it for?
Use it to check or format Go, TypeScript, Python, Rust, and other supported project code, across the whole project or a selected area.
Why use it?
It removes the need to remember which tools a project uses and helps ensure formatting happens before lint checks. It can optionally apply allowed fixes directly to files.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to check or format Go, TypeScript, Python, Rust, and other supported project code, across the whole project or a selected area.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/random6913/claude-code-superkit/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.

Clone the repo
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkit

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/random6913/claude-code-superkit/lint/github.svg)](https://agentmods.dev/commands/random6913/claude-code-superkit/lint)
Your own site
<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/lint"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/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/commands/random6913/claude-code-superkit/lint"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,063 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.00021 $0.02063
Opus 5.5 $0.00008 $0.00825
Sonnet 5.5 $0.00004 $0.00413
Haiku 4.5 $0.00002 $0.00206

Measured 1mo ago against content hash 023fddd2e6ee, 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.

packages/core/commands/lint.md · 138 lines

How it starts

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

Lint

Role

Auto-detect the project's formatters and linters from stack-marker files and run them — optionally scoped to backend or frontend, optionally in --fix mode.

Hard Rules

  • Run the formatter before the linter for each stack (format first, then check).
  • Prefer a Makefile lint / fmt target over the raw tool when one exists — it may carry project-specific setup.
  • Run only the commands in the Step 2 table (and the Step 4 --fix variants); never invent linters, flags, or tools not listed there.
  • Treat --fix as a modifier combinable with any scope, not as a scope of its own.
  • --fix rewrites files in place — apply it only to the Step 4 format and auto-fix commands, never to check-only commands (go vet, tsc --noEmit, mypy, flake8).
  • Report every detected in-scope linter, including PASS and unavailable ones; one block per detected in-scope linter.
  • Default to scope all for empty or unrecognized input — never guess a narrower scope.

Step 1 — Parse Arguments

Read the request and derive two independent values from it. Scope and fix are orthogonal: any scope may carry --fix.

$ARGUMENTS

  • scope = the first bare token equal to backend, frontend, or all. Empty input or any unrecognized token → all.
  • fix = true if the token --fix appears anywhere in the input, else false.

Done-when: scope is exactly one of backend / frontend / all, and fix is true or false.

Step 2 — Detect Linters

Scan the project for stack markers and map each present marker to its commands. Detect with Bash only: test -f <marker> for files, grep -qF '<section>' pyproject.toml for a config section (fixed-string -F so the [...] in section names like [tool.ruff] is matched literally, not as a regex character class), command -v <tool> for a tool on PATH.

Marker Format Command Lint Command Stack
go.mod gofmt -w . go vet ./... Go
go.mod + golangci-lint in PATH gofmt -w . golangci-lint run Go (extended)
package.json + .eslintrc* / eslint.config.* — npx eslint . ESLint
package.json + tsconfig.json — npx tsc --noEmit TypeScript
package.json + prettier config (.prettierrc*, prettier.config.*, or a prettier key in package.json) npx prettier --write . npx prettier --check . Prettier
pyproject.toml + [tool.ruff] ruff format . ruff check . Python (ruff)
pyproject.toml + [tool.black] black . — Python (black)
pyproject.toml + [tool.flake8] / setup.cfg — flake8 Python (flake8)
pyproject.toml + [tool.mypy] — mypy . Python (mypy)
Cargo.toml cargo fmt cargo clippy -- -D warnings Rust
Makefile with lint target — make lint Makefile
Makefile with fmt target make fmt — Makefile

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

  1. 1mo ago First seen · 138 lines · 21 tokens per session scan A 023fddd2e6ee

Subscribe to this mod's changes

lint is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 2,063 once invoked, about $0.0001 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.