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 instructions/leeguooooo/claude-code-usage-bar/agents-mdgit clone --depth 1 https://github.com/leeguooooo/claude-code-usage-barWhat 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.00636 | $0.00636 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
claude-code-usage-bar AGENTS.md 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Core code lives in
src/claude_statusbar:core.pyhandles usage calculation and model lookup,cli.pyprovides the entrypoint (claude-statusbar,cstatus,cs), andupdater.pymanages self-upgrades. - Packaging metadata is in
pyproject.toml; built artifacts land indist/(keep generated wheels/sdists out of commits unless releasing). - Installer helpers:
install.shandweb-install.shfor one-line setup,uninstall.shfor cleanup, andpublish.shfor PyPI uploads. Demo and promotional assets sit indemo/,img.png, andpromotion/.
Build, Test, and Development Commands
- Install for development (editable):
python -m pip install -e . - Run locally:
claude-statusbar(orpython -m claude_statusbar.cli --versionto verify wiring). - Build distribution:
python -m build(requiresbuild/wheel). - Publish to PyPI:
./publish.sh(expectsPYPI_API_TOKENor~/.pypirc; offers TestPyPI first). - Install optional dependency for richer data:
python -m claude_statusbar.cli --install-depsthen follow prompts forclaude-monitor.
Coding Style & Naming Conventions
- Python 3.9+; follow PEP 8 with 4-space indentation and short, imperative helper names (
get_current_model,try_original_analysis). - Keep dependencies minimal (stdlib only by default); guard optional imports and subprocess calls.
- Prefer pure functions with clear return types; add
typinghints where missing and keep logging quiet (current default ERROR).
Testing Guidelines
- No automated suite exists yet; add targeted
pytestcases aroundcore.main, calculation helpers, and file parsing when you touch logic. - For manual checks: place sample Claude JSONL data under
~/.claude/projects/, runclaude-statusbar, and confirm token/cost figures and reset timer behave as expected across empty/malformed files. - If introducing flags, verify CLI help stays readable:
python -m claude_statusbar.cli --help.
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 First seen · 33 lines · 636 tokens per session scan A 3ddfc5bbafe1
claude-code-usage-bar AGENTS.md is an instructions file published in the GitHub repository leeguooooo/claude-code-usage-bar (358 stars, last pushed 7d ago), licensed MIT. It adds 636 tokens to every session, about $0.0032 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-30.
Other instructions, from other repositories
Skill_Seekers CLAUDE.md
Instructions for yusufkaraaslan/Skill_Seekers, covering claude.md, project overview, essential commands, required before running tests or cli (src/ layout) and run all tests (never skip - all must pass before commits).
Skill_Seekers AGENTS.md
Instructions for yusufkaraaslan/Skill_Seekers, covering agents.md - skill seekers, project overview, key capabilities, setup and with dev tools (pytest, ruff, mypy, coverage).
octocode AGENTS.md
AGENTS.md instructions for bgauryy/octocode, covering agents.md — octocode monorepo, dogfood, architecture, packages and tools.
octocode CLAUDE.md
Claude Code instructions for bgauryy/octocode: Read AGENTS.md. Discover repository skills under .agents/skills and activate only those matching the task.
che-ical-mcp AGENTS.md
AGENTS.md instructions for PsychQuant/che-ical-mcp, covering spectra instructions, use $spectra- skills when, workflow and parked changes.
claude-for-designers CLAUDE.md
Instructions for mshadmanrahman/claude-for-designers, covering claude for designers: how to work in this folder, what this folder is, when the student asks about the folder, orient them, work out which class they are on before you answer and answer keys: never open one unasked.