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/fix-bug/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/fix-bug)<a href="https://agentmods.dev/skills/tddworks/claudebar/fix-bug"><img src="https://agentmods.dev/badge/skills/tddworks/claudebar/fix-bug/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/fix-bug"><img src="https://agentmods.dev/badge/skills/tddworks/claudebar/fix-bug.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.00078 | $0.02301 |
| Opus 5.5 | $0.00031 | $0.00920 |
| Sonnet 5.5 | $0.00016 | $0.00460 |
| Haiku 4.5 | $0.00008 | $0.00230 |
Grade A, and why
fix-bug 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Bug in ClaudeBar
Fix bugs using Chicago School TDD, root cause analysis, and rich domain design.
Workflow
┌─────────────────────────────────────────────────────────────┐
│ 1. REPRODUCE & UNDERSTAND │
├─────────────────────────────────────────────────────────────┤
│ • Reproduce the bug │
│ • Identify expected vs actual behavior │
│ • Locate the root cause in code │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 2. WRITE FAILING TEST (Red) │
├─────────────────────────────────────────────────────────────┤
│ • Write test that exposes the bug │
│ • Test should FAIL before fix │
│ • Test should verify CORRECT behavior │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 3. FIX & VERIFY (Green) │
├─────────────────────────────────────────────────────────────┤
│ • Implement minimal fix │
│ • Test now PASSES │
│ • All existing tests still pass │
└─────────────────────────────────────────────────────────────┘
Phase 1: Reproduce & Understand
Identify the Bug
- Reproduce: Follow exact steps to trigger the bug
- Expected: What SHOULD happen (the person's mental model — USER_JOURNEYS)
- Actual: What IS happening (current behavior)
- Root cause: WHY it's happening (code analysis)
For a provider that shows the wrong thing or fails:
- The log:
~/Library/Logs/ClaudeBar/ClaudeBar.log(infoand above) — which data source answered, which step failed (lookup · fetch · mapping);debuggoes to OSLog only (troubleshooting). - The failed step:
account.lastFailedStepandlastErrorsay whether the key, the request or the reading broke — fix that piece. - The real response: capture the CLI's or API's actual answer, redacted (no token, email, name or real usage), as the test's fixture. Never log a token, key or cookie while investigating.
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 · +2 lines 0599a47c2f5d
- 15d ago Changed · +12 lines b493bacc3125
- 21d ago Changed · +4 lines 9b8566e62bf5
- 22d ago Changed · +11 lines a834fc7d6301
- 23d ago Changed 1496eed68284
- 25d ago Changed · +10 lines 30510cb5f0a7
- 1mo ago Changed 16753f8fa31d
- 1mo ago First seen · 173 lines · 78 tokens per session scan A 3a44100328f3
fix-bug is a skill published in the GitHub repository tddworks/ClaudeBar (1,557 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 2,301 once invoked, about $0.0003 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
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.
polya-fix
Phase 5 of the Pólya Heuristic Coder: First-Principles Bug Remediation, Seam Tracing, Bisection Search (O(log n)), Failing Reproduction Tests, and Incubation Circuit-Breaker Gate (docs/bug-reports/{slug}-bugfix.md).
tdd-bug-report
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans enforcing the Prove-It pattern (failing regression test first) with rollback strategies.
triage-issue
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.