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/add-provider/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/add-provider)<a href="https://agentmods.dev/skills/tddworks/claudebar/add-provider"><img src="https://agentmods.dev/badge/skills/tddworks/claudebar/add-provider/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/add-provider"><img src="https://agentmods.dev/badge/skills/tddworks/claudebar/add-provider.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.00111 | $0.05608 |
| Opus 5.5 | $0.00044 | $0.02243 |
| Sonnet 5.5 | $0.00022 | $0.01122 |
| Haiku 4.5 | $0.00011 | $0.00561 |
Grade A, and why
add-provider 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Provider to ClaudeBar
A provider is data: one file, Modules/Providers/Resources/Providers/<id>.json.
The app finds it — ProviderCatalog.detect() reads every definition in the
bundle (and in ~/.claudebar/providers, ~/.claudebar/extensions) and makes
each on one shared Engine (TARGET_ARCHITECTURE §10).
There is no registration step and no Swift line that names it.
It is an abstraction layer that answers three questions, each once: who the
provider is (profile), how an account is signed in (settings, and
accounts when the vendor keeps a login in a folder), and how to get its
usage (dataSources: where the key is, how to fetch, how to read the
answer). One
Provider class and one DataSource type run every definition. You write
no Swift for a vendor: no XxxProvider, no XxxUsageProbe, no
XxxCredentialLoader.
Read first: TARGET_ARCHITECTURE.md (how a definition runs), MODULAR_DESIGN.md (which module a file goes in), and CANONICAL_MODEL.md (the words). Every built-in provider is a definition, so there is a worked example for most shapes: an API key with a region (
minimax.json), a CLI's login file renewed by OAuth (grok.json) or by the CLI itself (gemini.json), a TUI (kimi.json), a browser session over several requests (alibaba.json), an app's local server (antigravity.json), cloud metrics priced into money (bedrock.json). Their tests are inModules/Providers/Tests/.
The docs are the source of truth (AGENTS.md). A provider that fits the definition language needs no design change. One that needs the language to grow — a new case and worker, a new capability (CANONICAL §2.1), a new setting kind — is a design change: write it into TARGET_ARCHITECTURE / CANONICAL_MODEL first and ask the user to confirm before writing code.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 c8e79bf3e8f0
- 9d ago Changed · +69 lines d6bc4480c334
- 22d ago Changed · +13 lines b204ab72d342
- 23d ago Changed · +8 lines ed5cc17d96bf
- 24d ago Changed · +30 lines · -4 tokens per session a204f545d23b
- 26d ago Changed · -122 lines · +26 tokens per session b8446b01ff73
- 1mo ago Changed 54b54515056f
- 1mo ago First seen · 338 lines · 89 tokens per session scan A 46f54cdf4a88
add-provider is a skill published in the GitHub repository tddworks/ClaudeBar (1,557 stars, last pushed yesterday), licensed Apache-2.0. It adds 111 tokens to every session and 5,608 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.