A macOS menu bar application that monitors AI coding assistant usage quotas. Keep track of your Claude, Codex, Antigravity ,and Gemini usage at a glance.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 51%
Response Time: -
First Timer Success: 56%
tddworks/ClaudeBar has a recorded first-timer success rate of 55.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tddworks/ClaudeBar respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 59.8 places tddworks/ClaudeBar in the A tier.
The external contributor pull request merge rate for tddworks/ClaudeBar is 50.6%, based on public PR activity from non-core contributors.
tddworks/ClaudeBar does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in tddworks/ClaudeBar. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/tddworks/ClaudeBar?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (63% approval). Large PRs (>500 lines) take ~115 hours (23% approval). Keep your diff compact for rapid review.
Part of #331. Move Kiro (kiro) from its hand-written provider and probe to a JSON definition run by the generic Provider and DataSource, as #329 did for Claude and Codex. What it does today kiro-cli with input /usage\n/quit\n as a plain process (not a PTY), timeout 30s Bonus credits: used/total → weekly, expires in N days → reset now + N days Credits (used of total → Monthly, resets on MM/DD → this year's date, next year if past No match → parseFailed("No quota data found in Kiro CLI output") What the definition will need a non-PTY CLI fetch (also Oh My Pi) text mapping: left = capture ÷ capture, relative "in N days" and MM/DD resets — or a script with humanDate() Each ability goes into Modules/DataSources generically, test-first, and gets a row in TARGET_ARCHITECTURE §8.1 — never vendor-named Swift, never a Probe name. Shared needs are tracked in the epic. Must keep working providers.kiro.isEnabled the UI, unchanged Done when Modules/Providers/Resources/Provide
Part of #331. Move Amp (ampcode) from its hand-written provider and probe to a JSON definition run by the generic Provider and DataSource, as #329 did for Claude and Codex. What it does today amp usage --no-color (PTY), timeout 8s; non-zero exit → executionFailed Email from Signed in as (\S+) ( Credit line <label>: $x / $y remaining → model quota, left = x / y; balance line <label>: $x remaining → 100% with dollarRemaining Labels: "amp free" → Free, "individual credits" → Individual No lines → parseFailed("No valid credit lines found in amp usage output") What the definition will need text mapping: left = capture ÷ capture, money rows, label renames — or a small script honour the CLI's exit code a balance with no ceiling (Left law) Each ability goes into Modules/DataSources generically, test-first, and gets a row in TARGET_ARCHITECTURE §8.1 — never vendor-named Swift, never a Probe name. Shared needs are tracked in the epic. Must keep working providers.ampcode.is
Part of #331. Move Vercel AI Gateway (vercel-gateway) from its hand-written provider and probe to a JSON definition run by the generic Provider and DataSource, as #329 did for Claude and Codex. What it does today GET https://ai-gateway.vercel.sh/v1/credits, Bearer, timeout 30s Key: env var from vercel.authEnvVar (default AI_GATEWAY_API_KEY), then ClaudeBar Keychain vercel-ai-gateway-api-key balance (number or numeric string) → AI Gateway Credits quota with dollarRemaining; percentRemaining always 100 401/403: "Vercel rejected the API key. New keys may take a moment to activate." Config card: env var name, save/delete key What the definition will need setting credential + env var name from a setting a balance with no ceiling (Left law, slice 4) Each ability goes into Modules/DataSources generically, test-first, and gets a row in TARGET_ARCHITECTURE §8.1 — never vendor-named Swift, never a Probe name. Shared needs are tracked in the epic. Must keep working vercel.authEnvVar Key
Part of #331. Move DeepSeek (deepseek) from its hand-written provider and probe to a JSON definition run by the generic Provider and DataSource, as #329 did for Claude and Codex. What it does today GET https://api.deepseek.com/user/balance, Authorization: Bearer <key>, timeout 30s Key: env var named by deepseek.authEnvVar (default DEEPSEEK_API_KEY), then ClaudeBar's saved key (com.claudebar.credentials.deepseek-api-key) Maps balance_infos[0].total_balance (decimal string, billing currency) to a Balance quota; percentRemaining 100, or 0 when is_available is false; subtitle Paid: ¥x · Granted: ¥y Empty balance_infos → noData; bad amount → parseFailed Config card: env var name, save/delete key What the definition will need setting credential (key saved by ClaudeBar) and env var name from a setting a balance with no ceiling and a currency from the response — waits on the Left law (slice 4) or keeps today's 100% until then the 0-when-unavailable rule and the paid/granted subtitl
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to tddworks/ClaudeBar, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of tddworks/ClaudeBar acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.6% were successfully merged into the primary branch.
tddworks/ClaudeBar has a recorded first-timer success rate of 55.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 59.8 places tddworks/ClaudeBar in the Welcoming tier.
The external pull request merge rate is 50.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
tddworks/ClaudeBar does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for tddworks/ClaudeBar are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.