agentleFS
emtcmcaemtcmca/claude-for-legal-billing/skills/rate-card/SKILL.md

rate-card

Skill1 starsChanged 3 months agoMITView on GitHub

View and update billing rates — default hourly rates per attorney, client-specific overrides, billing arrangements (hourly, flat fee, contingency), and billing increments. Use when onboarding a new client, renegotiating a rate, or reviewing what rates are configured.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 7 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.claude/plugins/config/claude-for-legal/billing/CLAUDE.md.

    line 25
  2. Very specific:

    Read all files in [billing_data_path]/attorneys/.

    line 37
  3. Distinctive:

    Update an attorney's default rate, billing increment, or LEDES timekeeper settings.

    line 71
  4. Very specific:

    Read [billing_data_path]/attorneys/[slug].yaml.

    line 73
  5. Distinctive:

    Ask what to change: rate, increment, timekeeper ID, timekeeper classification, or any combination.

    line 75
  6. Distinctive:

    Write updated YAML. Confirm before writing.

    line 78
  7. Distinctive:

    Read the attorney YAML. Read the client YAML.

    line 89
  8. Distinctive:

    Ask: "Rate for [attorney] on [client] matters: $___/hr (press enter to remove override and use default)"

    line 91
  9. Very specific:

    If yes, offer to update the client's arrangement field (hourly | flat-fee | contingency | no-charge | courtesy).

    line 95
  10. Very specific:

    If flat-fee: ask for the flat amount and update budget_cap in the client YAML with a note.

    line 96
  11. Distinctive:

    Update client-level settings: billing arrangement, budget cap, retainer balance, and LEDES client ID.

    line 102
  12. Very specific:

    Read [billing_data_path]/clients/[slug].yaml.

    line 104
  13. Distinctive:

    Ask what to change. Include:

    line 106
  14. Very specific:

    If provided, write ledes_client_id: [value] to the client YAML.

    line 108
  15. Very specific:

    Create attorney profiles from scratch — that's in /billing-legal:cold-start-interview

    line 136
  16. Very specific:

    Create client profiles from scratch — that's in /billing-legal:time-entry, on the first entry for a new client.

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/billing-legal:rate-card

When this runs

Attorney wants to view or update rates. Subcommands: list, set, override.

Instructions

Preflight - read /billing-legal:billing-guardrails first. It carries the approval gate, the append-only record rule, UTBMS field discipline, and the boundary on what this plugin records rather than decides. Where it conflicts with the steps below, the stricter rule wins.

1. Read config

Read ~/.claude/plugins/config/claude-for-legal/billing/CLAUDE.md. Get billing_data_path. Check for placeholders — if present, stop and direct to cold-start.

2. Dispatch on subcommand

Parse $ARGUMENTS. First token is the subcommand.


list (default if no subcommand)

Show the current rate configuration in a readable table.

Read all files in [billing_data_path]/attorneys/. For each attorney, show:

  • Default rate
  • Billing increment
  • All client-specific overrides

Then read all files in [billing_data_path]/clients/. For each client, show:

  • Billing arrangement
  • Budget cap
  • Which attorney has a client-specific override (and what it is)

Output:

## Rate Card

### Attorneys

| Attorney | Default Rate | Increment | Client Overrides |
|---|---|---|---|
| Alice Jones | $350/hr | 0.1h (6 min) | Acme Corp: $325/hr |
| Bob Smith | $275/hr | 0.1h (6 min) | — |

### Clients

| Client | Arrangement | Budget Cap | Notes |
|---|---|---|---|
| Acme Corp | Hourly | $15,000 | Prefers monthly invoices |
| Beta LLP | Flat fee | — | $5,000 flat for trademark search |

set --attorney <slug>

Update an attorney's default rate, billing increment, or LEDES timekeeper settings.

  1. Read [billing_data_path]/attorneys/[slug].yaml. If not found, list available attorneys.
  2. Show current values including timekeeper_id and timekeeper_classification if set.
  3. Ask what to change: rate, increment, timekeeper ID, timekeeper classification, or any combination.
    • Timekeeper ID: "Timekeeper ID (used in LEDES exports — typically a bar number or firm-assigned ID; press enter to use attorney slug as default)"
    • Timekeeper classification: "Timekeeper classification (AT = attorney, PA = paralegal, OF = of counsel, CL = law clerk — default: AT)"
  4. Write updated YAML. Confirm before writing.

After writing:

Updated for [name]. New entries will use the updated settings. Existing pending entries are not affected — to adjust them, use /billing-legal:wip-review.


override --attorney <slug> --client <slug>

Set or update a client-specific rate override for an attorney.

  1. Read the attorney YAML. Read the client YAML.
  2. Show the current override if one exists.
  3. Ask: "Rate for [attorney] on [client] matters: $___/hr (press enter to remove override and use default)"
  4. Write the update.

Also ask: "Is this a special billing arrangement for this client?"

  • If yes, offer to update the client's arrangement field (hourly | flat-fee | contingency | no-charge | courtesy).
  • If flat-fee: ask for the flat amount and update budget_cap in the client YAML with a note.

override --client <slug>

Update client-level settings: billing arrangement, budget cap, retainer balance, and LEDES client ID.

  1. Read [billing_data_path]/clients/[slug].yaml. If not found, do NOT create it here — say: "No profile for [slug] yet. Client profiles are created on the first time entry. Run /billing-legal:time-entry for this client, then come back to set rates and overrides." Then stop.
  2. Show current values including ledes_client_id if set.
  3. Ask what to change. Include:
    • LEDES client ID: "LEDES client ID (the ID this client uses in their e-billing system, e.g., ACME-001. Press enter to use the default derived from the client slug.)"
    • If provided, write ledes_client_id: [value] to the client YAML.

Changing arrangement to flat-fee:

Setting a flat-fee arrangement means the billing panel will still track time for your records, but will not show hourly calculations. The flat amount should be set as the budget cap. Confirm?

Changing arrangement to contingency:

Contingency matters: time is tracked for records, but the rate is $0 (no fees until settlement or verdict). Budget warnings are suppressed. Confirm?

Updating budget cap:

  • Show current amount and running WIP total.
  • Warn if the new cap is below the current WIP total.

Billing arrangements

ArrangementHow billing panel behavesInvoice shows
hourlyShows hours × rate = amountHours, rate, and amount
flat-feeShows hours tracked; no dollar mathHours only (dollar line reads "Flat fee matter")
contingencyShows hours tracked; $0 rateHours only (dollar line reads "Contingency matter — no current fees")
no-chargePanel suppressed unless --forceNot billable
courtesyPanel shows time; notes courtesy statusHours only with "Courtesy — not billed" note

What this skill does not do

  • Create attorney profiles from scratch — that's in /billing-legal:cold-start-interview
  • Create client profiles from scratch — that's in /billing-legal:time-entry, on the first entry for a new client. That is the only path that creates a client.
  • Show or generate invoices — use /billing-legal:invoice-generate

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.