coderabbit-cost-tuning — Claude Code skill for cost reviews
The coderabbit-cost-tuning skill reviews CodeRabbit plans, seats, limits, and usage against current billing evidence. Use it to prepare cost scenarios before anyone approves a change.
MIT 1 installs ★ 2,935 updated 2026-10-29
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a claude-codeWhat coderabbit-cost-tuning does
The skill builds a period-based view of CodeRabbit billing: plan and cadence, assigned seats, add-on status, and observed usage. It separates unused seats from avoidable overage, repository scope, and capacity needs. Since prices and allowances can change, the review relies on current plan and contract evidence rather than fixed figures.
Its output includes a dated baseline and keep, right-size, and upgrade scenarios, with expected impact, an owner, an effective date, and rollback constraints. Changes stay in a local draft until the organization owner and billing owner approve them. The skill does not use file tools as a substitute for authenticated CodeRabbit or Git-provider operations.
What it helps with
- spot inactive seats before a plan change
- compare a higher tier with usage-based credits
- separate avoidable overage from capacity needs
- prepare cost scenarios with owners and rollback conditions
Example prompts for the agent
- Review current CodeRabbit billing and suggest ways to reduce the cost.
- Find inactive CodeRabbit seats before we change plans.
- Compare a higher plan with usage credits using current billing evidence.
How to install coderabbit-cost-tuning
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a claude-code2Manually: put the files in place
~/.claude/skills/coderabbit-cost-tuning/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/coderabbit-cost-tuning/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a codex2Manually: put the files in place
.agents/skills/coderabbit-cost-tuning/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a cursor2Manually: put the files in place
.cursor/skills/coderabbit-cost-tuning/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/coderabbit-cost-tuning2Manually: put the files in place
.github/skills/coderabbit-cost-tuning/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/coderabbit-cost-tuningManually: put the files in place
.devin/skills/coderabbit-cost-tuning/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about coderabbit-cost-tuning
How do I install coderabbit-cost-tuning in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill coderabbit-cost-tuning -a claude-code. The skill file is at ~/.claude/skills/coderabbit-cost-tuning/SKILL.md.
What does coderabbit-cost-tuning do?
It reviews CodeRabbit billing and usage for a chosen period, then lays out cost scenarios and a recommendation for approval.
Can the skill change a plan or remove seats on its own?
No. Buying credits, changing plans, removing seats, or changing access requires approval from the billing owner and organization owner. Until then, it produces a local draft and evidence plan.
Source text
SKILL.md · MIT
--- name: coderabbit-cost-tuning description: >- Review plan, seat, limit, and pay-as-you-go usage from current billing evidence without hard-coded prices. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "reduce CodeRabbit cost". allowed-tools: Read,Glob,Grep,Write,Edit version: 2.0.0 argument-hint: "[target] [evidence-or-scope]" model: inherit effort: high author: Jeremy Longshore <[email protected]> license: MIT compatibility: Requires current CodeRabbit documentation and approved access for any live organization, repository, billing, or API change tags: [saas, coderabbit, billing, cost-control, seats] --- # CodeRabbit Cost and Usage Review ## Overview Build an approval-ready cost decision from current dashboard and plan evidence. Prices, allowances, and entitlements are time-sensitive. ## Prerequisites - Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner. - Read `references/official-docs.md` and re-check any time-sensitive contract before execution. - Use synthetic or read-only evidence until the approval boundary is satisfied. - Preserve the repository's independent CI, security, and human-review requirements. ## Current Contract - The plans page is authoritative for current prices and hourly allowances. - Seats and administrative roles are separate controls. - The usage-based add-on can extend eligible PR and CLI reviews. - Mid-cycle changes can create prorated charges. ## Authentication Treat Git-provider sessions, CodeRabbit web sessions, CLI credentials, and CodeRabbit API keys as separate credentials. Use only an already-approved session or secret-manager reference, never print a secret, and do not place credentials in `.coderabbit.yaml`, source files, logs, or deliverables. ## Instructions 1. Capture plan, cadence, seats, add-on state, and usage for one period. 2. Separate unused seats, avoidable overage, repository scope, and capacity needs. 3. Model keep, right-size, and upgrade scenarios with dated prices. 4. Present savings, impact, owner, effective date, and rollback constraints. ## Tool Discipline - Use **Glob** to locate candidate configuration and evidence files without widening scope. - Use **Grep** to find relevant fields, commands, identifiers, and stale claims. - Use **Read** to inspect the smallest required files and authoritative evidence. - Use **Write** only for a new approved local draft or evidence artifact. - Use **Edit** only for a bounded approved change whose rollback is known. - Do not use these file tools as a substitute for authenticated CodeRabbit or provider operations. ## Approval Boundaries Never buy credits, change plans, remove seats, or alter access without billing and organization-owner approval. Keep analysis and drafts local until approval is explicit, and record who approved the action and its scope. ## Output A dated baseline, scenario table, evidence links, recommendation, and approval record. Include source dates, unknowns, and the exact boundary between observed fact and recommendation. ## Error Handling | Condition | Response | |---|---| | Current contract is unclear or docs disagree | Stop mutation, cite both sources, and request owner resolution. | | Required access or approval is missing | Produce a draft and evidence plan only. | | Validation or pilot behavior differs from expectation | Restore the prior state and retain the failed evidence. | | Output contains secrets or private code | Stop, quarantine the artifact, redact it, and notify the data owner. | ## Examples ### Example 1 Identify inactive assigned seats before a downgrade. ### Example 2 Compare a higher plan with usage credits using current evidence. ## Validation - Confirm every claim against the dated sources in `references/official-docs.md`. - Verify the requested scope, owner, approval, happy path, failure path, and rollback. - Re-read the effective configuration or provider state after any approved change. - Report unsupported fields, undocumented endpoints, and unverified assumptions as failures. ## Resources - [Official documentation and contract notes](references/official-docs.md) - Re-check the dated contract before any live operation. - Treat unresolved or changed vendor behavior as a stop condition.
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace