Agent skill

Billing

by trycompai in trycompai/comp

A skill your agent uses when changing Comp AI billing, Stripe products/prices, subscription checkout, org payment methods, entitlements, usage ledgers, invoices, or billing webhooks.

AGPL-3.0Auto-check passedBackend & APIs

Install Billing

skills CLI
$ npx skills add trycompai/comp --skill billing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install trycompai/comp billing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/billing .claude/skills/billing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
billing
GitHub stars
2k
Token cost
~824 tokens
SKILL.md length
351 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses when changing Comp AI billing, Stripe products/prices, subscription checkout, org payment methods, entitlements, usage ledgers, invoices, or billing webhooks.

  • Works in 7 steps: Add or update SKU definitions and Stripe… → Store Stripe IDs in the catalog by… → Create subscriptions through Stripe… → …
  • Changing Comp AI billing
  • SKILL.md covers Core Rules, Current SKU Shape, Implementation Pattern and Webhooks, plus 1 more section
  • Calls bun

What it does

Billing is an agent skill from trycompai/comp. Use when changing Comp AI billing, Stripe products/prices, subscription checkout, org payment methods, entitlements, usage ledgers, invoices, or billing webhooks.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Webhooks and Forms and invoices. It works with Stripe. The repository describes itself as: AI Native platform to get companies compliant - Vanta & Drata Alternative. The licence is AGPL-3.0.

When your agent uses it

  • Changing Comp AI billing
  • Stripe products/prices
  • Subscription checkout
  • Org payment methods

Example prompts

  • “/billing”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Add or update SKU definitions and Stripe IDs in packages/billing/src/index.ts and packages/billing/src/sku-definitions.ts.
  2. Store Stripe IDs in the catalog by environment rather than adding new env vars.
  3. Create subscriptions through Stripe Checkout mode: subscription.
  4. Use the shared Stripe customer default payment method unless the product explicitly needs overrides.
  5. For allowance products, sync local subscription state from Stripe subscription items and period timestamps.
  6. Record usage in the billing usage ledger with a stable idempotency key.
  7. Record support-relevant mutations in billing audit events.

What it can do on your machine

Read from SKILL.md and the folder at commit 0117612. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Billing loads about 824 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 351 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~824

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from trycompai/comp at commit 0117612, republished under its AGPL-3.0 licence (© trycompai). 351 words, ~824 tokens.

Download SKILL.mdSave it as .claude/skills/billing/SKILL.md (or your agent's skills folder).
name
billing
description
Use when changing Comp AI billing, Stripe products/prices, subscription checkout, org payment methods, entitlements, usage ledgers, invoices, or billing webhooks.
metadata.short-description
Comp AI billing architecture

Billing

Comp AI billing is SKU-first and subscription-ready. Stripe is the payment provider; Comp AI owns catalog definitions, entitlement state, usage gating, and audit history.

Core Rules

  • Use @trycompai/billing for SKU keys, amounts, Stripe product IDs, Stripe price IDs, cadence, and included usage.
  • Do not add product-specific nullable fields to OrganizationBilling.
  • Keep org-level billing generic: stripeCustomerId, stripePaymentMethodId, and paymentMethodUpdatedAt.
  • Store per-product state in generic per-SKU tables keyed by skuKey.
  • Gate paid actions from local entitlement/usage state, not directly from Stripe object reads.
  • Treat Stripe webhooks as eventually consistent, retryable, and possibly out of order.
  • Make webhook and entitlement handling idempotent with Stripe event IDs, invoice IDs, subscription item IDs, and period start/end.
  • Archive accidental live/test Stripe objects instead of reusing them blindly.

Current SKU Shape

  • Active background-check subscriptions: background_checks_monthly_3 ($79/mo, 3 checks), background_checks_monthly_10 ($199/mo, 10 checks), and background_checks_monthly_20 ($399/mo, 20 checks).
  • Active penetration-test subscriptions: pentest_monthly_1 ($299/mo, 1 scan), pentest_monthly_3 ($499/mo, 3 scans), and pentest_monthly_5_current ($899/mo, 5 scans).
  • Deprecated / legacy SKUs remain in the catalog for historical Stripe records: background_check_one_time, background_checks_monthly_25, pentest_monthly_4, pentest_monthly_5, and pentest_monthly_10.

Live catalog entries should only be added after deliberate live Stripe object creation.

Show full SKILL.md (164 more words)Show less

Implementation Pattern

  1. Add or update SKU definitions and Stripe IDs in packages/billing/src/index.ts and packages/billing/src/sku-definitions.ts.
  2. Store Stripe IDs in the catalog by environment rather than adding new env vars.
  3. Create subscriptions through Stripe Checkout mode: subscription.
  4. Use the shared Stripe customer default payment method unless the product explicitly needs overrides.
  5. For allowance products, sync local subscription state from Stripe subscription items and period timestamps.
  6. Record usage in the billing usage ledger with a stable idempotency key.
  7. Record support-relevant mutations in billing audit events.

Webhooks

Handle these events before launching subscription access:

  • checkout.session.completed
  • invoice.paid
  • invoice.payment_failed
  • invoice.payment_action_required
  • customer.subscription.updated
  • customer.subscription.deleted

Provision or renew allowance only for the matching subscription item and SKU. Do not use generic invoice-level periods for multi-item subscriptions.

Validation

  • Run bun run db:generate after Prisma schema changes.
  • Run bun run check:prisma-schemas to catch stale copied schema fragments.
  • Run catalog tests after SKU changes.
  • Add webhook tests for duplicate events, out-of-order delivery, payment failure, action required, cancellation, and renewal.

© trycompai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/billing of trycompai/comp.

Open the folder on GitHubat commit 0117612

Compare with similar skills

Billing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Billing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Billing this skilltrycompai/comp2k—~824Automated safety check: PassAGPL-3.0
Cashier Stripe Developmentluadotsh/lua3431 repos~1.2kAutomated safety check: PassMIT
Stripe Patternsbybren-llc/safe-agentic-workflow421—~1.2kAutomated safety check: PassMIT
Stripe Appsfossasia/eventyay1.7k2 repos~3.6kAutomated safety check: PassApache-2.0
Stripe Best Practiceskanchengw/cnllm1753 repos~925Automated safety check: PassApache-2.0
Stripe Best Practicesfossasia/eventyay1.7k1 repos~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling.

    343 GitHub starsUsed in 1 repo~1.2k tokens
    Backend & APIsAuto-check passed
  • Stripe Patterns

    bybren-llc/safe-agentic-workflow

    Stripe payment integration patterns for checkout flows, webhooks, and subscriptions.

    421 GitHub stars~1.2k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed
  • Stripe Apps

    fossasia/eventyay

    A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.

    1.7k GitHub starsUsed in 2 repos~3.6k tokens
    Backend & APIsAuto-check passed
  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    175 GitHub starsUsed in 3 repos~925 tokens
    Backend & APIsAuto-check passed
  • Stripe Best Practices

    fossasia/eventyay

    Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…

    1.7k GitHub starsUsed in 1 repo~1.7k tokens
    Backend & APIsAuto-check passed
  • Stripe Integration

    wshobson/agents

    Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks.

    40k GitHub starsUsed in 10 repos~1k tokens
    Backend & APIsAuto-check passed

More from trycompai/comp

All 31 skills in this repo
  • API Endpoint Contract

    trycompai/comp

    The contract every new or modified API endpoint must follow so it is correct for the public OpenAPI spec, the MCP server (npm @trycompai/mcp-server), the ValidationPipe, and the docs.

    2k GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Check Results Service

    trycompai/comp

    How to reuse ANY integration check's results in a feature via the universal CheckResultsService (apps/api integration-platform).

    2k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Data

    trycompai/comp

    A skill your agent uses when implementing data fetching, API calls, server/client components, or SWR hooks

    2k GitHub stars~955 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when SDK generation failed or seeing errors.

    2k GitHub stars~938 tokensUpdated today
    Auto-check passed
  • Forms

    trycompai/comp

    A skill your agent uses when building forms - covers React Hook Form, Zod validation, and form patterns

    2k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Code

    trycompai/comp

    A skill your agent uses when writing TypeScript/React code - covers type safety, component patterns, and file organization

    2k GitHub stars~909 tokensUpdated today
    Auto-check: warnings

Works with

Categories

Questions about Billing

What does Billing do?

A skill your agent uses when changing Comp AI billing, Stripe products/prices, subscription checkout, org payment methods, entitlements, usage ledgers, invoices, or billing webhooks. Billing is an agent skill from trycompai/comp. Use when changing Comp AI billing, Stripe products/prices, subscription checkout, org payment methods, entitlements, usage ledgers, invoices, or billing webhooks.

When should I use Billing?

Billing fits situations like: changing Comp AI billing; stripe products/prices; subscription checkout; org payment methods.

How do I install Billing in Claude Code?

Run `npx skills add trycompai/comp --skill billing -a claude-code`. Or copy the skill folder (.agents/skills/billing in trycompai/comp) into .claude/skills/billing in your project. Claude Code loads it when a task matches its description.

How do I install Billing in Codex?

Run `npx skills add trycompai/comp --skill billing -a codex`. Or copy the skill folder (.agents/skills/billing in trycompai/comp) into .agents/skills/billing in your project. Codex loads it when a task matches its description.

Can I use Billing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trycompai/comp --skill billing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/billing, .gemini/skills/billing, .github/skills/billing and .opencode/skills/billing in your project.

What does Billing need to run?

Going by SKILL.md and its folder, Billing needs the command-line tools its instructions call (bun).

Does Billing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Billing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Billing use?

Billing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Billing use?

About 824 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Billing?

Skills that share tags, products or a category with Billing: Cashier Stripe Development (luadotsh/lua, 343 stars), Stripe Patterns (bybren-llc/safe-agentic-workflow, 421 stars), Stripe Apps (fossasia/eventyay, 1.7k stars) and Stripe Best Practices (kanchengw/cnllm, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Billing?

trycompai (a GitHub organization) maintains it in trycompai/comp, which has 2,018 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.

Source: trycompai/comp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.