Borrowing it
Nothing to install: this file belongs to Mirage20/ccstatus-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Mirage20/ccstatus-go/main/.claude/commands/update-config.mdgit clone --depth 1 https://github.com/Mirage20/ccstatus-goWrote 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/mirage20/ccstatus-go/update-config)<a href="https://agentmods.dev/commands/mirage20/ccstatus-go/update-config"><img src="https://agentmods.dev/badge/commands/mirage20/ccstatus-go/update-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/mirage20/ccstatus-go/update-config"><img src="https://agentmods.dev/badge/commands/mirage20/ccstatus-go/update-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.00013 | $0.00523 |
| Opus 5.5 | $0.00005 | $0.00209 |
| Sonnet 5.5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
update-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 2mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Project: ccstatus-go - Claude Code statusline generator
- Architecture: Provider-Component pattern with self-registering plugins
- Config system: Uses Koanf with YAML format
- Config search order:
.claude/ccstatus.local.yaml- Project-specific local (gitignored).claude/ccstatus.yaml- Project-specific shared~/.claude/ccstatus.yaml- User default
Task
Scan the codebase to find all default configuration values and generate a comprehensive config.yaml file with:
-
Component Configuration
- Find all registered components in
internal/components/ - Extract default component order from
cmd/ccstatus/main.go - Extract settings from each component's
config.gofile - Document each component's template variables and options
- Find all registered components in
-
Provider Configuration
- Find all providers in
internal/providers/ - Extract default provider settings (cache TTL, etc.)
- Document provider-specific cache configurations
- Find all providers in
-
Core Configuration
- Find core settings in
internal/core/andcmd/ - Extract cache settings from
internal/cache/cache.go - Extract separator settings from
internal/core/statusline.go - Document global options and defaults
- Find core settings in
-
Structure the YAML with:
- Comprehensive header explaining config file locations
- Meaningful inline comments for each option
- Default values clearly marked
- Example configurations at the bottom
- Available color options documented
- Template function reference
Output
$ARGUMENTS
Generate the config file to the path provided above (default: config.yaml) with:
- All discovered default values from component/provider config.go files
- Comprehensive documentation comments explaining each option
- Proper YAML structure with consistent formatting
- Template variable documentation for each component
- Example configurations for common use cases
Implementation Steps
- Scan component registry and implementations for defaults
- Scan provider implementations for default settings
- Scan core configuration loading code for default values
- Scan for any hardcoded values that should be configurable
- Generate well-documented YAML with all findings
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.
- 2mo ago First seen · 64 lines · 13 tokens per session scan A 02171a30aa22
update-config is a command published in the GitHub repository Mirage20/ccstatus-go (11 stars, last pushed 27d ago), licensed MIT. It adds 13 tokens to every session and 523 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-30.
Other commands, from other repositories
configure
Configure HUD display options (layout, language, presets, display elements) while preserving advanced manual overrides.
review
Review current changes for correctness, style, and potential issues.
fix
Auto-fix linting, formatting, and common issues.
new-adr
Creates a numbered architecture decision record from a title.
explain-error
Explains an error found in a log file and proposes a next step.
code-review
Review the current branch changes for bugs and style issues.