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/q1343135559/ClaudeMeterWrote 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/q1343135559/claudemeter/configure)<a href="https://agentmods.dev/commands/q1343135559/claudemeter/configure"><img src="https://agentmods.dev/badge/commands/q1343135559/claudemeter/configure.svg" alt="Measured on agentmods" 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.01541 |
| Opus 5 | $0.00005 | $0.00771 |
| Sonnet 5 | $0.00002 | $0.00308 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
configure 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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClaudeMeter Configure
Walk the user through adjusting ClaudeMeter's display configuration. Talk to them in whatever language they are using.
1. Read the current configuration
The config file lives at {CLAUDE_CONFIG_DIR:-~/.claude}/claudemeter/config.json.
CONFIG_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
cat "$CONFIG_DIR/claudemeter/config.json" 2>/dev/null || echo '{}'
A missing file is normal and means every value is at its default.
2. Ask what they want to change
Use AskUserQuestion, at most four questions at a time. Worthwhile directions:
- Which segments to show: line 1 (model / path / branch / cost), the context bar, the 5-hour window, the weekly window, per-model windows
- Only certain models:
scopedFilter— e.g.["Fable"]shows only Fable's weekly window - Bar width:
auto(adapts to terminal width), a fixed cell count, or0(percentages only) - When bars change colour:
thresholds.warning(default 50, turns yellow) andthresholds.critical(default 80, turns light red) - Labels: rename
CTX/5H/WEEK - Path depth:
pathLevels - Staleness threshold:
staleWarnMs - Background refresh:
autoRefresh— whether the statusline may startclaude -p /usagein the background (at most every five minutes) so per-model windows such as FABLE keep updating
Show the values currently in effect before asking.
3. Write the configuration back
Change only the keys the user asked about; preserve everything else. Some advanced keys
(colors, thresholds, staleMaxMs, maxWidth) are not part of this guided flow, but if the
user has set them by hand they must survive the write.
CONFIG_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
mkdir -p "$CONFIG_DIR/claudemeter"
Read the existing file, mutate that object, and write it back. Do not rebuild it from scratch.
4. Verify
CONFIG_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
COLUMNS=120 node "$CONFIG_DIR/claudemeter/launcher.mjs" --demo
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.
- 3d ago Changed · +8 lines f29120f5d729
- 7d ago First seen · 115 lines · 9 tokens per session scan A 925bc0726279
configure is a command published in the GitHub repository q1343135559/ClaudeMeter (1 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 1,541 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
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ccc-orchestrate
Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
design
A command that turns an existing plan into a detailed technical design for building the feature.
audit-project-github
This file contains GitHub integration for /audit-project.