config

A command for viewing or changing the current code-standards settings. These settings control enabled languages, code-size and complexity limits, and whether analysis runs after edits.

In plain words
What is it for?
Use it to inspect settings, change supported options such as file-length or complexity thresholds, enable or disable analysis, or start interactive reconfiguration.
Why use it?
It makes the project's rules visible and lets you adjust them without editing the configuration file by hand.

Command

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/hculap/better-code/config
Clone the repo
git clone --depth 1 https://github.com/hculap/better-code
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 824 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.00009 $0.00824
Opus 5 $0.00005 $0.00412
Sonnet 5 $0.00002 $0.00165
Haiku 4.5 $0.00001 $0.00082

Measured yesterday against content hash 9dbb6a4ec247, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

config 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 yesterday.

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/config.md · 149 lines

How it starts

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

Code Standards Configuration

View or modify current code-standards settings.

Usage Modes

View Mode (no arguments)

If $ARGUMENTS is empty, display current configuration:

  1. Read .claude/code-standards.local.md
  2. Parse YAML frontmatter
  3. Display in readable format:
## Current Code Standards Configuration

**Status:** Enabled/Disabled
**Active Analysis:** Yes/No

### Languages
- TypeScript/JavaScript
- Python
- Go

### Thresholds
| Metric | Value | Level |
|--------|-------|-------|
| File LOC | 400 | Standard |
| Function LOC | 50 | Standard |
| Complexity | 15 | Standard |

### Integrations
- CLAUDE.md: Yes

### Settings File
Location: `.claude/code-standards.local.md`

To modify, use `/code-standards:config set <key>=<value>`
Or run `/code-standards:init` to reconfigure interactively.

If no settings file exists, inform user and suggest running /code-standards:init.

Edit Mode (with arguments)

If $ARGUMENTS contains set key=value, modify the setting:

Supported keys:

  • enabled - true/false
  • active_analysis - true/false
  • file_loc - number (file LOC threshold)
  • function_loc - number (function LOC threshold)
  • complexity - number (complexity threshold)

Example usage:

/code-standards:config set file_loc=500
/code-standards:config set active_analysis=false
/code-standards:config set complexity=12

Edit Process

  1. Read current .claude/code-standards.local.md
  2. Parse YAML frontmatter
  3. Update the specified key
  4. Write back the file
  5. Confirm the change

Example output:

Updated `file_loc` from 400 to 500.

New configuration:
- File LOC threshold: 500
- Function LOC threshold: 50
- Complexity threshold: 15

Interactive Edit Mode

If $ARGUMENTS is edit or interactive, use AskUserQuestion to let user modify settings interactively:

Question 1: "What would you like to change?"

  • Options: Thresholds, Languages, Active analysis, Everything

Based on selection, ask follow-up questions to update specific settings.

Read the full file on GitHub · 149 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. yesterday First seen · 149 lines · 9 tokens per session scan A 9dbb6a4ec247

Subscribe to this mod's changes

config is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 824 once invoked, about $0.0000 per session on Opus 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.