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/setup)<a href="https://agentmods.dev/commands/hculap/better-code/setup"><img src="https://agentmods.dev/badge/commands/hculap/better-code/setup/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/setup"><img src="https://agentmods.dev/badge/commands/hculap/better-code/setup.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.00013 | $0.00735 |
| Opus 5.5 | $0.00005 | $0.00294 |
| Sonnet 5.5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
setup 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards Setup
Configure the documentation framework for this project. First-run setup or reconfiguration of existing settings.
Process
Step 1: Check Existing Configuration
Read .claude/doc-master.local.md if it exists to check current settings.
Step 2: Framework Selection
If no existing configuration or --reset flag provided, ask the user to choose:
-
Diátaxis (Recommended) - Modern four-quadrant approach
- Tutorials (learning-oriented)
- How-to guides (task-oriented)
- Explanations (understanding-oriented)
- Reference (information-oriented)
- Best for: Products with diverse user bases, growing documentation
-
Traditional - Hierarchical structure
- Overview
- Getting Started
- API Reference
- Examples
- FAQ
- Best for: Developer tools, API-first projects, smaller codebases
-
Custom - Organization-specific standards
- User provides source (local folder or URL)
- Agent analyzes and creates rules
- Best for: Teams with existing documentation standards
Step 3: Custom Standards Setup (if selected)
If user selects Custom:
-
Ask for source location:
- Local folder path (e.g.,
/path/to/standards/) - URL (e.g.,
https://docs.company.com/style-guide)
- Local folder path (e.g.,
-
Fetch and analyze source materials:
- For local folder: Read all markdown files
- For URL: Fetch content with WebFetch
-
Extract rules for:
- Writing style and voice
- Document structure requirements
- Terminology preferences
- Quality criteria
- Templates
-
Generate comprehensive rules in the configuration file
Step 4: Proactive Agents Configuration
Ask user if documentation agents should trigger proactively:
- Yes (default): Agents auto-trigger when user asks to document backend, frontend, API, etc.
- No: User must explicitly request doc-master agents
Step 5: Save Configuration
Write configuration to .claude/doc-master.local.md:
---
standard: diataxis | traditional | custom
proactive_agents: true | false
custom_source: null | /path | https://url
---
# Project Documentation Notes
[For custom: Include extracted rules and style guide]
[For all: Space for project-specific notes]
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 · 118 lines · 13 tokens per session scan A 6c9eca9a3fdf
setup is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 735 once invoked, about $0.0001 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-status
Quick status check cho Latent Chain Mode và current workflow.