An interactive setup command for choosing which programming languages and code rules a project should use. It saves those choices in the project's settings and can add the rules to CLAUDE.md, a file that gives coding guidance to Claude.

Use it when installing or reconfiguring the code-standards add-on, enabling analysis after edits, setting file and function limits, and choosing whether to update CLAUDE.md.

It avoids manually creating configuration and helps ensure the checker matches the project's languages and preferred strictness.

init — 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/init/github.svg)](https://agentmods.dev/commands/hculap/better-code/init)

Your own site

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

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

When invoked 699 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.00009	$0.00699
Opus 5.5	$0.00004	$0.00280
Sonnet 5.5	$0.00002	$0.00140
Haiku 4.5	$0.00001	$0.00070

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

Security

Grade A, and why

init 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/init.md · 113 lines

How it starts

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

Code Standards Initialization

Set up the code-standards plugin for this project. Walk the user through configuration options interactively.

Setup Process

Step 1: Check Existing Configuration

Check if .claude/code-standards.local.md already exists:

test -f .claude/code-standards.local.md && echo "EXISTS" || echo "NEW"

If EXISTS, inform user and ask whether to reconfigure or keep existing settings.

Step 2: Gather Preferences

Use AskUserQuestion to ask the user about their preferences:

Question 1 - Languages:

Ask: "Which languages should be checked?"
Options: TypeScript/JavaScript, Python, Go, Java, Ruby, All common languages
Allow multi-select

Question 2 - Active Analysis:

Ask: "Enable proactive analysis after code edits?"
Options: Yes (recommended), No

Question 3 - Thresholds:

Ask: "Which threshold strictness level?"
Options:
- Relaxed (larger files/functions allowed)
- Standard (recommended defaults)
- Strict (smaller limits, stricter complexity)

Question 4 - CLAUDE.md Integration:

Ask: "Add code standards rules to CLAUDE.md?"
Options: Yes (recommended), No

Step 3: Create Settings File

Create .claude/code-standards.local.md with YAML frontmatter based on user choices.

Relaxed thresholds:

thresholds:
  file_loc: 600
  function_loc: 80
  complexity: 20

Standard thresholds:

thresholds:
  file_loc: 400
  function_loc: 50
  complexity: 15

Strict thresholds:

thresholds:
  file_loc: 250
  function_loc: 30
  complexity: 10

Step 4: Update CLAUDE.md (if requested)

If user wants CLAUDE.md integration, append a ## Code Standards section:

## Code Standards

This project uses the code-standards plugin for quality enforcement.

### Size Limits
- Files: Target [X] LOC, max [Y] LOC
- Functions: Target [A] LOC, max [B] LOC
- Complexity: Max cyclomatic complexity [N]

### Principles
Follow KISS, DRY, YAGNI, and SRP principles.

### Review Checklist
- [ ] File/function sizes within limits
- [ ] One responsibility per module
- [ ] No silent error handling
- [ ] Tests cover important behavior

Read the full file on GitHub · 113 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 · 113 lines · 9 tokens per session scan A 4c1ea0cbf44d

Subscribe to this mod's changes

init is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 699 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 ai-tools code-quality dev-tools documentation plugins

sync-config

Sync a scraping config's URLs against the live documentation site.

yusufkaraaslan/Skill_Seekers · 11 tokens

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

init