lint-test

lint-test is a command for Claude Code from iBrain-BVBA/gutt-claude-code-plugin. It costs 0 tokens per session (536 once invoked), scanned A, original, MIT.

A command that runs code formatting checks, linting, type checks, and tests before a commit.

In plain words
What is it for?
Use /lint-test for normal checks, --fix to automatically correct supported lint issues, or --watch to keep tests running as files change.
Why use it?
It gathers common quality checks in one workflow and reports whether the project appears ready to commit.

Command for Claude Code

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.

agentmods
npx agentmods add commands/ibrain-bvba/gutt-claude-code-plugin/lint-test
Clone the repo
git clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-plugin

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-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test.svg)](https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test)
Your own site
<a href="https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/lint-test.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 536 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00536
Opus 5 $0.00000 $0.00268
Sonnet 5 $0.00000 $0.00107
Haiku 4.5 $0.00000 $0.00054

Measured 4d ago against content hash 44633a0d58e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lint-test 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 4d 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.

.claude/commands/lint-test.md · 111 lines

What it actually says

Lint and Test Command

/lint-test - Run linting and tests before committing.

Usage

/lint-test
/lint-test --fix    # Auto-fix lint issues
/lint-test --watch  # Watch mode for tests

Workflow

Step 1: Check Memory for Project Standards

search_memory_nodes(query="coding standards linting", entity="WorkingAgreement", max_nodes=5)

Step 2: Run Linting

Python:

# Format check
black --check src/ tests/

# Lint
flake8 src/ tests/

# Type check
mypy src/

TypeScript/JavaScript:

# Lint
npm run lint

# Type check (TypeScript)
npm run typecheck

Step 3: Run Tests

Python:

pytest tests/ -v --tb=short

TypeScript/JavaScript:

npm test

Step 4: Report Results

## Lint & Test Results

### Linting
- Formatter: PASS (or X files need formatting)
- Linter: PASS (or X issues found)
- Type check: PASS (or X type errors)

### Tests
- Total: X tests
- Passed: X
- Failed: X
- Skipped: X

### Verdict: READY TO COMMIT / NEEDS FIXES

Auto-Fix Mode (--fix)

# Python
black src/ tests/
isort src/ tests/

# JavaScript/TypeScript
npm run lint -- --fix

Default Commands by Language

Language Lint Test
Python black --check . && flake8 . && mypy . pytest -v
TypeScript npm run lint && npm run typecheck npm test
JavaScript npm run lint npm test
Go go fmt ./... && go vet ./... go test ./...

Pre-Commit Integration

If .pre-commit-config.yaml exists, run:

pre-commit run --all-files

Exit Codes

  • 0 - All checks pass, ready to commit
  • 1 - Lint or test failures, needs fixes
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. 4d ago First seen · 111 lines · 0 tokens per session scan A 44633a0d58e5

Subscribe to this mod's changes

lint-test is a command published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 tokens. 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.