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.
npx agentmods add commands/hculap/better-code/checkgit clone --depth 1 https://github.com/hculap/better-codeWhat 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 | $0.00006 | $0.01186 |
| Opus 5 | $0.00003 | $0.00593 |
| Sonnet 5 | $0.00001 | $0.00237 |
| Haiku 4.5 | $0.00001 | $0.00119 |
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 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.
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 ifstatementsfor,while,loopiterationscase,when,switchbranches&&,||logical operatorscatch,except,rescueexception 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]
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.
- yesterday First seen · 151 lines · 6 tokens per session scan A ba18a5cbf60d
check is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 1,186 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.
Other commands, from other repositories
create-skill
Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).
sync-config
Sync a scraping config's URLs against the live documentation site.
create_plan
Create detailed implementation plans through interactive research and iteration.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
research_codebase
Document codebase as-is with thoughts directory for historical context.
iterate_plan
Iterate on existing implementation plans with thorough research and updates.