What is finance-billing-ops?

An evidence-based workflow for understanding revenue, pricing, refunds, team billing, and what billing code actually does. It focuses on operational facts rather than relying only on a product website or sales description.

Use it to review sales and refund activity, compare pricing models, investigate duplicate charges, check team-seat and quota logic, and verify checkout and customer entitlements.

It helps find differences between promised and implemented billing behavior, such as whether seat-based pricing or usage limits really work as described.

finance-billing-ops — Skill for Claude Code and Codex by Jamkris

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Jamkris/everything-gemini-code --skill finance-billing-ops

Clone the repo

git clone --depth 1 https://github.com/Jamkris/everything-gemini-code

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/finance-billing-ops/github.svg)](https://agentmods.dev/skills/jamkris/everything-gemini-code/finance-billing-ops)

Your own site

<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/finance-billing-ops"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/finance-billing-ops/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/finance-billing-ops"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/finance-billing-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 789 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

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.00053	$0.00789
Opus 5.5	$0.00021	$0.00316
Sonnet 5.5	$0.00011	$0.00158
Haiku 4.5	$0.00005	$0.00079

Measured 1mo ago against content hash c270d67c2f68, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

finance-billing-ops 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 1mo 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.

Origin

This is a copy

92% identical to finance-billing-ops — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/finance-billing-ops/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Finance Billing Ops

Use this when the user wants to understand money, pricing, refunds, team-seat logic, or whether the product actually behaves the way the website and sales copy imply.

This is broader than customer-billing-ops. That skill is for customer remediation. This skill is for operator truth: revenue state, pricing decisions, team billing, and code-backed billing behavior.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

customer-billing-ops for customer-specific remediation and follow-up
research-ops when competitor pricing or current market evidence matters
market-research when the answer should end in a pricing recommendation
github-ops when the billing truth depends on code, backlog, or release state in sibling repos
verification-loop when the answer depends on proving checkout, seat handling, or entitlement behavior

When to Use

user asks for Stripe sales, refunds, MRR, or recent customer activity
user asks whether team billing, per-seat billing, or quota stacking is real in code
user wants competitor pricing comparisons or pricing-model benchmarks
the question mixes revenue facts with product implementation truth

Guardrails

distinguish live data from saved snapshots
separate:
- revenue fact
- customer impact
- code-backed product truth
- recommendation
do not say "per seat" unless the actual entitlement path enforces it
do not assume duplicate subscriptions imply duplicate value

Workflow

1. Start from the freshest billing evidence

Prefer live billing data. If the data is not live, state the snapshot timestamp explicitly.

Normalize the picture:

paid sales
active subscriptions
failed or incomplete checkouts
refunds
disputes
duplicate subscriptions

2. Separate customer incidents from product truth

If the question is customer-specific, classify first:

duplicate checkout
real team intent
broken self-serve controls
unmet product value
failed payment or incomplete setup

Read the full file on GitHub · 128 lines

Changes

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.

1mo ago First seen · 128 lines · 53 tokens per session scan A c270d67c2f68

Subscribe to this mod's changes

finance-billing-ops is a skill published in the GitHub repository Jamkris/everything-gemini-code (91 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 789 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to finance-billing-ops, differing in 28 lines, and is treated as a copy.

Debugging Finance and fintech ai-agents antigravity developer-tools gemini-cli gemini-cli-extension gemini-cli-skills

google-cloud-storage-diagnostic

Troubleshoots and diagnoses Google Cloud Storage (GCS) errors, permission denials, and access control issues. Use when a user encounters a 403 Permission Denied error on a Google Cloud bucket or object, or needs help diagnosing and resolving GCS IAM bindings, ACLs, UBLA, or service agent configurations.

gemini-cli-extensions/google-cloud-storage · 72 tokens

finance-billing-ops