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.
git clone --depth 1 https://github.com/hculap/better-codeWrote 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.
[](https://agentmods.dev/commands/hculap/better-code/config)<a href="https://agentmods.dev/commands/hculap/better-code/config"><img src="https://agentmods.dev/badge/commands/hculap/better-code/config/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.
<a href="https://agentmods.dev/commands/hculap/better-code/config"><img src="https://agentmods.dev/badge/commands/hculap/better-code/config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00824 |
| Opus 5.5 | $0.00004 | $0.00330 |
| Sonnet 5.5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00082 |
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 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.
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:
- Read
.claude/code-standards.local.md - Parse YAML frontmatter
- 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/falseactive_analysis- true/falsefile_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
- Read current
.claude/code-standards.local.md - Parse YAML frontmatter
- Update the specified key
- Write back the file
- 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.
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 · 149 lines · 9 tokens per session scan A 9dbb6a4ec247
config 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 824 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.
Other commands, from other repositories
sync-config
Sync a scraping config's URLs against the live documentation site.
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…
sm-swab
Run slop-mop's iterative development loop for this repository.
ccg-latent
Latent Chain Mode for structured, token-efficient reasoning with hidden-state management.
latent-fix
Quick fix cho file đang mở hoặc file được chỉ định. Tối đa 1-2 patches.
latent-review
Quick latent review of code using structured hidden-state reasoning.