ClaudeBar is a macOS menu bar application that displays remaining quotas, credits, balances, and reset times for AI coding services. It is for developers who use services such as Claude, Codex, Gemini, Copilot, or Cursor and want to monitor their usage from one place.
Borrowing it
Nothing to install: this file belongs to tddworks/ClaudeBar. 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/tddworks/ClaudeBar/main/.claude/skills/improvement/SKILL.mdgit clone --depth 1 https://github.com/tddworks/ClaudeBarWrote 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/skills/tddworks/claudebar/improvement)<a href="https://agentmods.dev/skills/tddworks/claudebar/improvement"><img src="https://agentmods.dev/badge/skills/tddworks/claudebar/improvement/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/skills/tddworks/claudebar/improvement"><img src="https://agentmods.dev/badge/skills/tddworks/claudebar/improvement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.02132 |
| Opus 5.5 | $0.00036 | $0.00853 |
| Sonnet 5.5 | $0.00018 | $0.00426 |
| Haiku 4.5 | $0.00009 | $0.00213 |
Grade A, and why
improvement 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 4d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve ClaudeBar Feature
Make improvements to existing functionality using TDD and rich domain design.
When to Use This vs Other Skills
| Scenario | Skill to Use |
|---|---|
| Enhance existing behavior | improvement (this skill) |
| Fix broken behavior | fix-bug |
| Add new feature | implement-feature |
| Add new AI provider | add-provider |
| A new report card over usage history | add-report |
Workflow
┌─────────────────────────────────────────────────────────────┐
│ 0. CHECK THE DESIGN (docs are the source of truth) │
├─────────────────────────────────────────────────────────────┤
│ • Read USER_JOURNEYS, CANONICAL, TARGET, design.md │
│ • Think the domain: how should it be? (domain-shape.md) │
│ • Does the improvement change a law, an owner, a word? │
│ • If so: write it into the docs, ask the user to confirm │
└─────────────────────────────────────────────────────────────┘
│
▼ (design confirmed, or unchanged)
┌─────────────────────────────────────────────────────────────┐
│ 1. UNDERSTAND CURRENT STATE │
├─────────────────────────────────────────────────────────────┤
│ • Read existing code │
│ • Understand current behavior │
│ • Identify what to improve │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 2. WRITE TEST FOR IMPROVED BEHAVIOR (Red) │
├─────────────────────────────────────────────────────────────┤
│ • Test describes the IMPROVED behavior │
│ • Test should FAIL initially │
│ • Keep existing tests passing │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 3. IMPLEMENT & VERIFY (Green) │
├─────────────────────────────────────────────────────────────┤
│ • Implement the improvement │
│ • New test PASSES │
│ • All existing tests still pass │
└─────────────────────────────────────────────────────────────┘
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.
- 4d ago Changed · +1 lines 7fdbf40b6a4d
- 15d ago Changed · +10 lines eb6006b49200
- 21d ago Changed · -3 lines e5626d183294
- 22d ago Changed · +19 lines d85edd376ce7
- 23d ago Changed d680d7fd76c7
- 25d ago Changed · +19 lines 09876818283f
- 1mo ago Changed d527c3069601
- 1mo ago First seen · 191 lines · 89 tokens per session scan A e14141d36cfd
improvement is a skill published in the GitHub repository tddworks/ClaudeBar (1,557 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 2,132 once invoked, about $0.0004 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 skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new functionality, adding behavior, or fixing bugs during active development.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
autonomous-tdd-debugger
Empowers the agent to autonomously run tests, read terminal stack traces, and self-heal code until tests pass. Transforms the agent from a passive coder to an active CI pipeline debugger.