A code-checking command that reviews source files for oversized files, long functions, and high decision complexity.

Use it after coding changes to inspect TypeScript, JavaScript, Python, Go, Java, Ruby, Rust, PHP, or Swift files and find areas worth simplifying.

It gives you concrete warnings about code that may be becoming difficult to understand or maintain. You can check a file or directory against project settings or default limits.

check — Command for Claude Code by hculap/better-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.

Clone the repo

git clone --depth 1 https://github.com/hculap/better-code

Made for: Claude Code.

Or install code-standards, the plugin that ships this one along with the rest of its 1 skill, 5 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hculap/better-code/check/github.svg)](https://agentmods.dev/commands/hculap/better-code/check)

Your own site

<a href="https://agentmods.dev/commands/hculap/better-code/check"><img src="https://agentmods.dev/badge/commands/hculap/better-code/check/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/hculap/better-code/check"><img src="https://agentmods.dev/badge/commands/hculap/better-code/check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,186 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.

Model	Per session	Once invoked
Fable 5.1	$0.00006	$0.01186
Opus 5.5	$0.00002	$0.00474
Sonnet 5.5	$0.00001	$0.00237
Haiku 4.5	$0.00001	$0.00119

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

Security

Grade A, and why

check 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/code-standards/commands/check.md · 151 lines

How it starts

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

Code Standards Check

Analyze $ARGUMENTS against code standards thresholds.

If no argument provided, analyze the current directory.

Analysis Process

Step 1: Load Settings

Read .claude/code-standards.local.md if it exists to get configured thresholds. If not found, use default thresholds:

File LOC: 400 (warning), 800 (critical)
Function LOC: 50 (warning), 80 (critical)
Complexity: 15 (warning), 20 (critical)

Step 2: Validate Target Path

If $ARGUMENTS is provided, verify the path exists:

If path does not exist:

Error: Path not found: `[path]`

Please verify the path exists. Use `/code-standards:check .` to analyze current directory.

If path exists but no source files found in directory:

No analyzable source files found in `[path]`

Supported: *.ts, *.tsx, *.js, *.jsx, *.py, *.go, *.java, *.rb
Excluded: node_modules, vendor, .git, dist, build

Step 3: Identify Target Files

If $ARGUMENTS is a single file, analyze that file. If $ARGUMENTS is a directory, find all source files:

TypeScript/JavaScript: *.ts, *.tsx, *.js, *.jsx
Python: *.py
Go: *.go
Java: *.java
Ruby: *.rb
Rust: *.rs
PHP: *.php
Swift: *.swift
Kotlin: *.kt
C#: *.cs

Exclude common directories: node_modules, vendor, .git, dist, build, __pycache__

Step 4: Analyze Each File

For each file:

Count lines of code (exclude blank lines and comments where possible)
Identify functions/methods and their line counts
Estimate cyclomatic complexity based on:
- if, else, elif, else if statements
- for, while, loop iterations
- case, when, switch branches
- &&, || logical operators
- catch, except, rescue exception handlers
- Ternary operators ? :

Step 5: Report Violations

Output a structured markdown table:

## Code Standards Report

**Target:** $ARGUMENTS
**Files analyzed:** [count]
**Violations found:** [count]

### Violations

| File | Issue | Severity | Line | Suggestion |
|------|-------|----------|------|------------|
| `src/service.ts` | File exceeds 600 LOC (742) | Warning | - | Split by domain responsibility |
| `src/service.ts:45` | Function `processOrder` exceeds 80 LOC (112) | Critical | 45-157 | Extract helper functions |
| `src/utils.ts:89` | Complexity >15 in `handleRequest` (18) | Warning | 89 | Simplify conditionals or extract |

### Summary

- **Critical:** [count] issues (must fix)
- **Warning:** [count] issues (should address)
- **Info:** [count] notes (consider)

### Recommendations

[Based on violations, provide 2-3 specific refactoring suggestions]

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

1mo ago First seen · 151 lines · 6 tokens per session scan A ba18a5cbf60d

Subscribe to this mod's changes

check is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 8d ago), licensed MIT. It adds 6 tokens to every session and 1,186 once invoked, about $0.0000 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.

Claude Code Code review ai-tools code-quality dev-tools documentation plugins

sm-buff

You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…

ScienceIsNeato/slop-mop · 0 tokens

check